All Apps and Add-ons

field extractions with delims

a212830
Champion

Hi,

I'm trying to create some fields using the DELIM option in transforms.conf. My file is whitespace separated, and here are my props/transforms:

props:
[bcoat_proxysg_streaming]
REPORT-main=delimExtractions
TRANSFORMS-sourcetype = nullPound
MAX_TIMESTAMP_LOOKAHEAD = 20
SHOULD_LINEMERGE = false
TZ = UTC

transforms:
[nullPound]
REGEX = ^#
DEST_KEY=queue
FORMAT=nullQueue

[delimExtractions]
DELIMS=" "
FIELDS="date", "time", "c-ip", "cs-username", "sc-filter-result", "cs-method", "cs-uri", "sc-status", "cs(Referer)", "cs-categories", "cs-auth-group", "x-exception-
id", "s-action", "cs(User-Agent)", "x-duration", "sc-bytes", "cs-bytes", "cs-uri-scheme", "cs-host", "cs-uri-port", "cs-uri-path", "cs-uri-query", "cs-uri-extension
", "protocol", "transport", "channelURL"

This looks pretty basic to me, but the fields aren't being shown in the SH. The files are being processed on a HF and sent to an indexer. I put these entries on the HF.

Am I missing something?

Tags (1)
0 Karma
1 Solution

Takajian
Builder

There are two types of field extractions which are search time field extraction and index time field extraction. Your delimExtraction is for search time extraction, not index time. Therefore, you should put it on SH, not HF. Please note that your nullqueue setting is processed in index time, so it should be left on HF. Please try this and confirm if it solve the issue.

View solution in original post

Takajian
Builder

There are two types of field extractions which are search time field extraction and index time field extraction. Your delimExtraction is for search time extraction, not index time. Therefore, you should put it on SH, not HF. Please note that your nullqueue setting is processed in index time, so it should be left on HF. Please try this and confirm if it solve the issue.

a212830
Champion

Worked! Thanks.

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Data Persistence in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. What happens if the OpenTelemetry collector ...

Thanks for the Memories! Splunk University, .conf25, and our Community

Thank you to everyone in the Splunk Community who joined us for .conf25, which kicked off with our iconic ...

Introducing Splunk 10.0: Smarter, Faster, and More Powerful Than Ever

Now On Demand Whether you're managing complex deployments or looking to future-proof your data ...