|
I'm trying to setup Fieldalias and not getting desire results. Here is what I have put into the props.conf file.
Am I missing something?? Thanks |
|
Your second Try adding an extension so that you have two unique entries:
Alternately, you can have both aliases in a single line. If you go that route, you will still override any previously defined value for Does it matter where in the props.conf file I input the FIELDALIAS information?
(17 Sep '10, 13:41)
wildbill4
It will have to be in a stanza that matches the sourcetype (or host, or source) for which you want to set the field alias. Other than that, it doesn't matter as long as it's a unique entry as above. If it's non-unique, then you have to worry about precedence rules, since another entry could override it (possibly from a different app). Also, I'm assuming you're only trying to use it within the search app -- if you need it across multiple apps you'll need to check the permissions and make sure it's set to global.
(17 Sep '10, 14:12)
southeringtonp ♦
Thanks for the assistance
(17 Sep '10, 14:13)
wildbill4
|
|
Unfortunately, field aliasing is one-to-one, and won't allow you to map many-to-one. The reason is that if orig_field doesn't exist, a blank value will be assigned to new_field. Consider an event that has only the acct field. Both FIELDALIAS directives will be evaluated. Lexicographically, FIELDALIAS-acct runs first and successfully aliases acct as account. But when FIELDALIAS-username runs it finds no User_Name field, so the result is the account field will be blank. There are two ways to work around this.
|
