- Splunk Answers
- :
- Splunk Administration
- :
- Knowledge Management
- :
- Re: Dealing with field names with a period in it
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi all, I have the following in a macro that I'm basically using to retrieve a integer value that will be used later in my search string:
| eval TestRxSNRTemp=split(Ipd.TestRxSNR," ")
| eval TestRxSNRValue=mvindex(TestRxSNRTemp,0)
The value of Ipd.TestRxSNR field will typically be a value like 20db. I just need the 20. Using the above does not yield the result I'm looking for. Unfortunately, the fields with the period in the name are in input files (XML files) that I don't have any controller over. I'm trying to figure out a way to work around this. I was wondering if there was a way to use the field name (with the period) as is? Thanks for your support.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry to be unclear. Basically all I needed was to use single quotes around the field name as you instructed. Works fine now. Thanks for your help.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Periods shouldn't pose a problem. Try using the rename command to rename one of your fields to include a .; no worries there.
There are a ton of ways to approach this. The first thought, personally, is to use regular expressions ! Here is but one way; if it doesn't work just post a comment and I'll revise.
There is a cool sed mode on the rex command, check it like this:
| rex field=Ipd.TestRxSNR mode=sed "s/[^0-9]//g"
What's this black magic? you screech? Ah, nothing but a global blank substitution for anything that isn't a number in the field we specify.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the suggestion. May try that one day. This time around the single quote did the trick.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry to be unclear. Basically all I needed was to use single quotes around the field name as you instructed. Works fine now. Thanks for your help.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm not entirely sure what you're asking here. To use fields with special characters in them in eval and where functions you'd use single quotes to refer to the fields. (E.x. 'lpd.TestRxSNR' ) If you're having trouble extracting a value, you could also consider the rex command to use a regular expression instead.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If possible, @acharlieh, please convert your comment to an answer and @hcastell, mark it as accepted. Thanks !
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Converted!
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry to be unclear. Basically all I needed was to use single quotes around the field name as you instructed. Works fine now. Thanks for your help.
Detecting Remote Code Executions With the Splunk Threat Research Team
Observability | Use Synthetic Monitoring for Website Metadata Verification
More Ways To Control Your Costs With Archived Metrics | Register for Tech Talk
