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!

Wondering How to Build Resiliency in the Cloud?

IT leaders are choosing Splunk Cloud as an ideal cloud transformation platform to drive business resilience,  ...

Updated Data Management and AWS GDI Inventory in Splunk Observability

We’re making some changes to Data Management and Infrastructure Inventory for AWS. The Data Management page, ...

Introducing the Splunk Community Dashboard Challenge!

Welcome to Splunk Community Dashboard Challenge! This is your chance to showcase your skills in creating ...