Splunk Search

How to dynamically create a field for each API with eventstats?

philip_102uk
Engager

I have an index with several API calls and I would like to dynamically create a field for each API which can then be used to create a timechart for each API call. My query looks like this:

| bucket span=1s _time | eventstats count AS TPS by _time

I want to have a TPS (transactions per second) for each API call, so TPS_api_pathsuffix where api_pathsuffix is the pathsuffix of each API. So effectively I want to have for each API call a table with all the TPSs for that API.

I would really appreciate any help you can give me.

0 Karma
1 Solution

sundareshr
Legend

Try this

| bucket span=1s _time | eventstats count AS TPS_api_pathsuffix by _time api_pathsuffix 

View solution in original post

sundareshr
Legend

Try this

| bucket span=1s _time | eventstats count AS TPS_api_pathsuffix by _time api_pathsuffix 

philip_102uk
Engager

Hi sundareshr,

I don't see how this is going to help me, can you please explain?

0 Karma

philip_102uk
Engager

Actually, having tested the proposed solution it seems to be working. I will continue testing and then accept it as the answer if it solves the problem.

0 Karma

philip_102uk
Engager

Thank you sundareshr, this has worked.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Where Innovation Takes Flight: The Splunk4Aviation Flight Sim Lands at .conf26

If you hear someone at .conf26 shouting "gear down, GEAR DOWN" across the show floor, you have found us.  The ...

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...