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!

Join Us for Splunk University and Get Your Bootcamp Game On!

If you know, you know! Splunk University is the vibe this summer so register today for bootcamps galore ...

.conf24 | Learning Tracks for Security, Observability, Platform, and Developers!

.conf24 is taking place at The Venetian in Las Vegas from June 11 - 14. Continue reading to learn about the ...

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...