Alerting

Docker log response time metrics

saireddy
Loves-to-Learn Lots

Can you please help, how to construct stats  metrics for the below docker logs.

ThreadID=124;ThreadIDHex=0000007c;ThreadName=[XNIO-2 task-32];Node=XXXXXX;TransID=;ConsumerSenderID=NA;URI=/getBaselinedcategorylist;ServiceName=findXXXX;TranasactionStartTime=;TransactionEndTime=2021-11-05 05:34:34.366;TotalResponseTime=;TransactionStatus=SUCCESS;Method=GET;StatusCode=200;ErrorMsg=;CaptureLocation=MicroserviceResponse;
ThreadID=124;ThreadIDHex=0000007c;ThreadName=[XNIO-2 task-32];Node=XXXXXX;TransID=;ConsumerSenderID=NA;URI=/getBaselinedcategorylist;ServiceName=findXXXX;TranasactionStartTime=2021-11-05 05:34:34.264;TransactionEndTime=;TotalResponseTime=;TransactionStatus=;Method=GET;StatusCode=;ErrorMsg=;CaptureLocation=MicroserviceRequest;


status should give transactioncount , transactionstatus, average, 90thP URI Method.

0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

What do you have so far?

For example, have you extracted the fields you are interested in or is that the part you need help with?

How do you know these two events are related to each other?

Has _time already been correctly extracted from the log entries for each event?

0 Karma

saireddy
Loves-to-Learn Lots

I tried something like this

index=docker_* source="/applogs/containers/fob*" 
| rex field=source "/applogs/containers/(?<ServiceName>.*?)\."
| stats count(ThreadIDHex) as "Transaction Count" min(_time) as starttime max(_time) as endtime range(_time) as duration by ServiceName URI

Regarding how they are related, threadid and threadihex for both the logs are same. 

Tags (2)
0 Karma

saireddy
Loves-to-Learn Lots

Can anyone help?

0 Karma
Get Updates on the Splunk Community!

Accelerating Observability as Code with the Splunk AI Assistant

We’ve seen in previous posts what Observability as Code (OaC) is and how it’s now essential for managing ...

Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...

 Splunk is More Than Just the Web Console For Digital Forensics and Incident Response (DFIR) practitioners, ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...