Deployment Architecture

Help bucketing time with mcollect?

daniel333
Builder

all,

I am running this search to collect exceptions by host. I am bucketing into 1min intervals. However when I go back with mstats or the metrics work bench - data is being time stamped at the point of the summary job run rather than at the _time of the bucket itself.

tag=java host=mydc* priority=error OR priority=warning OR priority=fatal java_exception=* role=* host=*abc*
| rex field=host (?<pod>\w\w\w\w\d\d)
| bin _time span=1m 
| stats first(_time) as _time count by pod,role,java_exception, priority
| rename count as _value 
| eval metric_name="dpw3.toyrus.java.exceptions.count"
| mcollect index=testmetrics 

The results table LOOKS fine. But the final product has the wrong time.

0 Karma
Get Updates on the Splunk Community!

Let’s Talk Terraform

If you’re beyond the first-weeks-of-a-startup stage, chances are your application’s architecture is pretty ...

Cloud Platform | Customer Change Announcement: Email Notification is Available For ...

The Notification Team is migrating our email service provider. As the rollout progresses, Splunk has enabled ...

Save the Date: GovSummit Returns Wednesday, December 11th!

Hey there, Splunk Community! Exciting news: Splunk’s GovSummit 2024 is returning to Washington, D.C. on ...