Refine your search:

1
1

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?

asked 24 Jun '11, 14:52

nick's gravatar image

nick ♦
14.2k1318
accept rate: 47%

edited 24 Jun '11, 14:53


One Answer:

I fully agree with that one

link

answered 01 Jul '11, 01:41

stepmmx's gravatar image

stepmmx
432
accept rate: 0%

Post your answer
toggle preview

Follow this question

Log In to enable email subscriptions

RSS:

Answers

Answers + Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "Title")
  • image?![alt text](/path/img.jpg "Title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×137
×98

Asked: 24 Jun '11, 14:52

Seen: 564 times

Last updated: 01 Jul '11, 01:41

Copyright © 2005-2012 Splunk, Inc. All rights reserved.