This is a challenge with any app which overrides fields that another app relies on. There are ways around it. Luckily, there’s actually not a ton of reliance on syslog events in the current UCS app.
What I recommend in the short term is to go into the Splunk_KB_CiscoUCS app. Make a local/ folder if you haven’t already. Open default/eventtypes.conf and copy the first three stanzas out to local/eventtypes.conf:
[ucs-syslog]
search = index=cisco_ucs sourcetype="ciscoucs:syslog"
description = Cisco UCS events received via syslog
[ucs-syslog-event]
search = index=cisco_ucs sourcetype="ciscoucs:syslog" mnemonic="EVENT"
description = Cisco UCS events received via syslog
[ucs-syslog-audit]
search = index=cisco_ucs sourcetype="ciscoucs:syslog" mnemonic="AUDIT"
description = Cisco UCS events received via syslog
And in each search line above, alter it to match what you need it to be to account for the IOS app’s overriding. I suggest perhaps a combination of sourcetype and host fields. Don’t forget that you can use macros here as well. So you could add a new macro, say call it cisco_ucs_manager_manager_hosts . Then your search lines might look like:
search= sourcetype=cisco:ios ` cisco_ucs_manager_manager_hosts`
I ship some macros in the main dashboard app, so you may want to put your macros there--but they can be stored anywhere that's in context for the users of the app. But for example, in SplunkAppForCiscoUCS/local/macros.conf:
[cisco_ucs_manager_manager_hosts]
definition = host=ucsmanager*
Or,
definition = host=host1 OR host=host2 OR host=host3
Obviously, you’ll need to edit the lines to suit your environment.
... View more