Splunk Search

How to stack all error codes per endpoints from a table?

dotekien
New Member

Context:
Each or transactions has its unique RequestId, and in Splunk search, we will have multiple rows with the same RequestId to describe all the activities of a given transaction.

Goal:
stack all error codes per endpoints so we can have a chart with the x-axis is endpoints and the y-axis are a count of errorCodes per endpoint

Here is my solution which I feel very close but still cannot get what I want 😞 Looking for your advice on either my solution or any other solutions. Thanks

Search query:

index=xyz sourcetype=tomcat_epf_app
[search index=xyz sourcetype=tomcat_epf_app "ERROR ControllerAdvice" OR "ERROR Reporter" | fields + RequestId | fields - _* | rename RequestId as search | format "" "" "OR" "" "OR" "" ] 
| rex "ErrorCode\-(?<code>\d{3,3})\-" 
| eval endpoints=case(searchmatch("/login"),"/login", searchmatch("/subscription"),"/subscription",searchmatch("/email"),"/email")
| table endpoints, RequestId, code | where isnotnull(code) OR isnotnull(endpoints) | sort str(RequestId)

Result:

alt text

0 Karma

koshyk
Super Champion

If you could put sample data, we could have put exactly as you requested, but assuming from your SPL, please try below (i've changed your SPL to be better performing)

index=xyz sourcetype=tomcat_epf_app ("ERROR ControllerAdvice" OR "ERROR Reporter" ) 
 | rex "ErrorCode\-(?<code>\d{3,3})\-" 
 | eval endpoints=case(searchmatch("/login"),"/login", searchmatch("/subscription"),"/subscription",searchmatch("/email"),"/email")
 | stats count(endpoints)  by RequestId

you can do chart also instead of stats

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!

[Puzzles] Solve, Learn, Repeat: Matching cron expressions

This puzzle (first published here) is based on matching timestamps to cron expressions.All the timestamps ...

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas     Cisco Live 2026 is almost here, and this ...

Data Management Digest – May 2026

Welcome to the May 2026 edition of Data Management Digest!   As your trusted partner in data innovation, the ...