Splunk Search

How to use "collect" and keep the timestamp and field extractions of the event?

jameshgibson
Path Finder

So I have used collect to save some events into a summary index. The problem is all of the timestamp information is lost which makes the info next to useless. It desides to default all the events to the search time.

It also drops all the field extractions that I set up which is a pain but can be worked around at a push.

pseudo search:

sourcetype=x my_field=name | rex=something "do_some_extractions" | collect index=summary
1 Solution

jameshgibson
Path Finder

The problem was that the _raw field came from a database and were not prefixed by a timestamp. So what I did in the end was add the following to prepend it:

my search | eval _raw=_time + ": " + _raw | collect index=summary

I don't have any way of adding the field extractions though that can be done at search time manually.

View solution in original post

jameshgibson
Path Finder

The problem was that the _raw field came from a database and were not prefixed by a timestamp. So what I did in the end was add the following to prepend it:

my search | eval _raw=_time + ": " + _raw | collect index=summary

I don't have any way of adding the field extractions though that can be done at search time manually.

LeeSart
Explorer

You sir are a genius!
I know this is an old post, but this is the only solution I've come across that fully solves the issue.
Pretty much every other post has some variation of | eval EventTime = _time, which is a decent workaround but doesn't preserve the _time field.

0 Karma
Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...