Splunk Search

Why does an ODBC query show a different result from the Splunk timechart report?

big_twilde
Engager

Hi,

I have a simple report/saved search with fixed time (-8@w1 to +1@w1) that calculates a timechart from a long list of 5min timespans with a binary up/down metric that reflects if that interval was OK.

| savedsearch KPI_BCP_Crawler_Delay | timechart span=1week avg(up) as up

Everything works fine, but partial values (i.e. current week) in the report seem to be handled differently once searched by ODBC.

While Splunk gives me ...

_time   up
...
7   2015-06-29  0.631448
8   2015-07-06  0.681052
9   2015-07-13  0.750000   <-- current week

... Excel/ODBC gives me:

_time   up
...
29.06.2015  0,631448
06.07.2015  0,681052
13.07.2015  0,949901 <--- different value than in Splunk, mostly near 1

Would be glad for a hint or a way how to debug this.

Best,
Thomas

0 Karma
1 Solution

big_twilde
Engager

Hi,

I found a workaround: the issue disappears, when you change the timeframe from (-8@w1 to +1@w1) to (-8@w1 to now).

Best,
Thomas

View solution in original post

big_twilde
Engager

Hi,

I found a workaround: the issue disappears, when you change the timeframe from (-8@w1 to +1@w1) to (-8@w1 to now).

Best,
Thomas

Get Updates on the Splunk Community!

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...

Cloud Monitoring Console - Unlocking Greater Visibility in SVC Usage Reporting

For Splunk Cloud customers, understanding and optimizing Splunk Virtual Compute (SVC) usage and resource ...

Automatic Discovery Part 3: Practical Use Cases

If you’ve enabled Automatic Discovery in your install of the Splunk Distribution of the OpenTelemetry ...