Getting Data In

missing sourcetype in index summary

JeToJedno
Explorer

I have two summary reports over an index, and one sourcetype is missing from one.

The reports are:
index="esam"
| eval fred=sourcetype.":".host
| eval time=strftime(_time,"%Y-%m-%d")
| stats count BY time, fred
| xyseries time, fred, count
and:
index="esam"
| eval date=strftime( _time, "%Y-%m-%d" ), channel=COALESCE(channel,' ')
| stats min(_time) AS min_time, max(_time) AS max_time, count BY sourcetype, date, channel, host
| fieldformat min_time=strftime(min_time, "%Y-%m-%d %H:%M:%S.%3N")
| fieldformat max_time=strftime(max_time, "%Y-%m-%d %H:%M:%S.%3N")

one sourcetype is present in the results of the first report and missing from the second.

Can you advise where to look for the problem?

Tags (2)
0 Karma

DalJeanis
Legend

most likely, there is a record with a sourcetype and no host. Update the second line of the second search to ...

 | eval date=strftime( _time, "%Y-%m-%d" ), channel=COALESCE(channel,' '), host=coalesce(host,"((missing))")
0 Karma

JeToJedno
Explorer

Thanks. I tried that. No change.

|time|ESAM:AT_messages:main|ESAM:break_decisioning:main|ESAM:break_evaluation:main|ESAM:break_return:main|ESAM:esam_server_debug:main|ESAM:scte104_splice_request_messages:main|ESAM:vicc_polling:main|ESAM:vicc_sanity_check:main|
|2018-06-05|7615438|18|27|16|3029470|11|57495|46|

and

|sourcetype|date|channel|host|min_time|max_time|count|
|ESAM:break_decisioning|2018-06-05|AD2|main|2018-06-05 08:43:50.641|2018-06-05 16:10:24.016|18|
|ESAM:break_evaluation|2018-06-05|AD2|main|2018-06-05 08:43:50.294|2018-06-05 16:10:13.902|27|
|ESAM:break_return|2018-06-05|AD2|main|2018-06-05 08:52:43.124|2018-06-05 16:12:00.352|16|
|ESAM:scte104_splice_request_messages|2018-06-05|AD2|main|2018-06-05 08:51:06.782|2018-06-05 16:10:24.016|11|
|ESAM:vicc_polling|2018-06-05|AD2|main|2018-06-05 00:00:02.328|2018-06-05 23:59:59.174|38336|
|ESAM:vicc_polling|2018-06-05|TEST|main|2018-06-05 00:00:02.795|2018-06-05 23:59:58.265|19159|
|ESAM:vicc_sanity_check|2018-06-05|AD2|main|2018-06-05 12:59:34.020|2018-06-05 13:37:44.024|6|

Note the ESAM:AT_messages:main present in the first and missing in the second.

0 Karma

skoelpin
SplunkTrust
SplunkTrust

Are you running over the same timerange?

0 Karma

JeToJedno
Explorer

Yes. -7d@d -> now
the logs (each sourcetype is a different set of log files) are all over the same timeperiod.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...

Splunk Developers: Construct Your Future at the .conf26 Builder Bar

Calling all Splunk architects, platform admins, and app developers: the site is open, and the blueprints are ...

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...