The add-on is available here on Splunkbase.
Please follow the provided instructions.
You might also want to read this part about "How to ask good questions".
Hope that helps - if it does I'd be happy if you would upvote/accept this answer, so others could profit from it. 🙂
... View more
Hey,
the easiest way should be a wildcard lookup, you can find a good explanation on that topic in this answer:
https://answers.splunk.com/answers/52580/can-we-use-wildcard-characters-in-a-lookup-table.html
You just need to switch the lookup type to wildcard, and append/prepend an * to your message text. 🙂
Hope that helps - if it does I'd be happy if you would upvote/accept this answer, so others could profit from it. 🙂
... View more
This is also only a problem if it happens constantly. If you only have it happen a few times, it might just be fluctuation in data input.
... View more
If you're running both on the same system, you might run into trouble because, by default, both want to listen on TCP 9997.
Check if both instances actually run, you might have to change the splunkd port of the UF using server.conf.
... View more
Depending on the compression tool you use (7-zip, WinRAR, etc) you might be able to set those permissions in the tar.gz file directly - you could check that.
... View more
Ah, yeah, that won't possible with that approach.
You could try and put
[global]
acceptFrom = whatever
in the restmap.conf, and just override in your own use case with a more specific stanza. You could also try putting that in a [default] stanza instead of global.
Its not explicitly mentioned in the doc, but sometimes things still work.
If you try this, please let us know if it worked!
... View more
You might get an easy success by using the sourcetype syslog. Syslog often uses the old timestamp style, without year and timezone, and that might end up in bad timestamp detection unless you use sourcetype syslog.
... View more
It should be possible, however I'd not advise to do this, as indexers shouldn't run such inputs. I'd suggest you either get one of your existing UFs or HFs to be able to access those SNMP targets, or setup another UF/HF in the right place so it's able to do this.
... View more
As far as I see this - because the TA ships with a eventgen.conf (which it shouldn't), and to correctly interpret such a config, Splunk would need the eventgen.conf.spec from the eventgen TA. As you don't have that it installed, it complains because it can't verify that .conf file. You can safely ignore this (and better, remove that eventgen.conf from the app at all).
... View more
Good spot! You still have to either remove the ?P because that's the start of a named capture group, and add FORMAT = yourfieldname::$1, or just add the fieldname after the ?P , like (?P<yourfieldname>yourregex)
... View more