Splunk Search

How to round a millisecond output?

heybails88
Path Finder

Does anyone know how to round a time readout from 00:07:06.53846153846155 to 00:07:06.54?

0 Karma
1 Solution

adonio
Ultra Champion

maybe like this:

| transaction node startswith="up_or_down=down" endswith="up_or_down=available"
| stats avg(duration) as avg_outage by node
| eval rounded_avg_outage = round(avg_outage, 2)
| eval MTTR = tostring(rounded_avg_outage, "duration)
| table node MTTR

hope it helps

View solution in original post

adonio
Ultra Champion

maybe like this:

| transaction node startswith="up_or_down=down" endswith="up_or_down=available"
| stats avg(duration) as avg_outage by node
| eval rounded_avg_outage = round(avg_outage, 2)
| eval MTTR = tostring(rounded_avg_outage, "duration)
| table node MTTR

hope it helps

heybails88
Path Finder

Excellent!! That worked. I appreciate it.

0 Karma

DalJeanis
Legend

What is the format of the underlying field? There are at least five different ways, but the efficiency will be based on the field format.

0 Karma

heybails88
Path Finder

Thanks for the response

Here's the base of the search with MTTR is the mean time to repair or average outage time averaged by duration. The "avg_outage" is epoch:

| transaction node startswith="up_or_down=down" endswith="up_or_down=available"
| stats avg(duration) as avg_outage by node
| eval MTTR=tostring(avg_outage, "duration")
| table node MTTR

0 Karma
Get Updates on the Splunk Community!

Modern way of developing distributed application using OTel

Recently, I had the opportunity to work on a complex microservice using Spring boot and Quarkus to develop a ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had 3 releases of new security content via the Enterprise Security ...

Archived Metrics Now Available for APAC and EMEA realms

We’re excited to announce the launch of Archived Metrics in Splunk Infrastructure Monitoring for our customers ...