Getting Data In

Multi-value fields not populating for index

ccollord
Explorer

Hello,
I think i'm doing something wrong, but i've read through all the manuals and can't figure out what it is!

I have an index named "email" that has entries that look like this:
[MAILTO][email protected] [MAILTO][email protected] [MAILFROM][email protected] [SUBJECT]Hi there! ....

In my props.conf file:
[email] <--- this is the name of my index
MAX_TIMESTAMP_LOOKAHEAD = 40
TZ=UTC
REPORT-email = email-mv

In my transforms.conf file:
[email-mv]
REGEX = ([[^\s]+])([^\t]+)
FORMAT = $1$2
MV_ADD = true

I've been trying various things all morning and then doing " index=email | extract reload=T ". Any ideas what i'm missing?
Thanks!
~Chris

0 Karma
1 Solution

Stephen_Sorkin
Splunk Employee
Splunk Employee

Two problems.

  1. props.conf must be in terms of sourcetype, source or host, not index.
  2. The format here should be $1::$2.

View solution in original post

0 Karma

ccollord
Explorer

Thank you! "email" was also my sourcetype name so i was okay there but the change to the FORMAT fixed it!

0 Karma

Stephen_Sorkin
Splunk Employee
Splunk Employee

Two problems.

  1. props.conf must be in terms of sourcetype, source or host, not index.
  2. The format here should be $1::$2.
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!

Developer Spotlight with Denis Gladkikh

From Splunk Engineer to Kubernetes App Builder Denis GladkikhWhat happens when a lifelong developer turns a ...

Governing Enterprise AI, Bringing Cisco Telemetry Home, and More from Splunk Lantern

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...