Getting Data In

Why are my fields Missing after upgrade?

cmcclure_splunk
Splunk Employee
Splunk Employee

After upgrading from 4.2 to 4.2.1 all my inputs do not seem to be working. My props.conf file and transforms.conf file have not changed. I also moved those files to etc\system\local from the "bundle" folder and restarted Splunk. The inputs are still not showing up.

1 Solution

cmcclure_splunk
Splunk Employee
Splunk Employee

You may want to try checking on each part of the files from the beginning to the end..

  1. Are your events being indexed by Splunk without any field extractions?
  2. If the event is parsed but the fields are not extracted, ensure that fields that are being used in props.conf are being found correctly (e.g. The host field matches the stanza in props.conf [host::123.456.789.001]) You may want to test this by creating a test stanza that points directly to the source, for example [source::/some/dir/with/a/test.file]
  3. Ensure that your transforms.conf contains the correct capture groups for extracting your variables, there are several ways to do this and you will want to check against the documentation for using config files to perform field extractions and also with the transforms.conf.spec
  4. You also want to make sure that you do not have the Field Discovery toggle set to "Off" as this will hide the extracted fields from the search UI. (see pictures below)

To see fields

Fields hidden

View solution in original post

cmcclure_splunk
Splunk Employee
Splunk Employee

You may want to try checking on each part of the files from the beginning to the end..

  1. Are your events being indexed by Splunk without any field extractions?
  2. If the event is parsed but the fields are not extracted, ensure that fields that are being used in props.conf are being found correctly (e.g. The host field matches the stanza in props.conf [host::123.456.789.001]) You may want to test this by creating a test stanza that points directly to the source, for example [source::/some/dir/with/a/test.file]
  3. Ensure that your transforms.conf contains the correct capture groups for extracting your variables, there are several ways to do this and you will want to check against the documentation for using config files to perform field extractions and also with the transforms.conf.spec
  4. You also want to make sure that you do not have the Field Discovery toggle set to "Off" as this will hide the extracted fields from the search UI. (see pictures below)

To see fields

Fields hidden

Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Take Action Automatically on Splunk Alerts with Red Hat Ansible Automation Platform

 Are you ready to revolutionize your IT operations? As digital transformation accelerates, the demand for ...

Calling All Security Pros: Ready to Race Through Boston?

Hey Splunkers, .conf25 is heading to Boston and we’re kicking things off with something bold, competitive, and ...

Beyond Detection: How Splunk and Cisco Integrated Security Platforms Transform ...

Financial services organizations face an impossible equation: maintain 99.9% uptime for mission-critical ...