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!

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI!Discover how Splunk’s agentic AI ...

Splunk Enterprise Security 8.x: The Essential Upgrade for Threat Detection, ...

Watch On Demand the Tech Talk on November 6 at 11AM PT, and empower your SOC to reach new heights! Duration: ...

Splunk Observability as Code: From Zero to Dashboard

For the details on what Self-Service Observability and Observability as Code is, we have some awesome content ...