Getting Data In

will future versions of WMI not prefix all the sourcetype values with wmi?

sideview
SplunkTrust
SplunkTrust

Just curious if this is in the roadmap. It's more than a little inconvenient that when people use WMI, the sourcetypes are all "WMI:foo", and when they dont, the sourcetype is just "foo".

I find myself having to make macros and cover both cases and either duplicate stanzas in props.conf, or pull out what I can into transforms.conf. And this all seems silly since the underlying data is otherwise identical. It looks like the sort of thing that is a 'less-than-best' practice, ie abusing the sourcetype field to sneak in some other metadata.

Also, has anyone tried sourcetype renaming to make this problem go away?

Tags (2)

stepmmx
Path Finder

I fully agree with that one

0 Karma
Get Updates on the Splunk Community!

Index This | Why did the turkey cross the road?

November 2025 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  🚀 Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Feel the Splunk Love: Real Stories from Real Customers

Hello Splunk Community,    What’s the best part of hearing how our customers use Splunk? Easy: the positive ...