Devices that think you know their name

What exactly is that talkers name is one of the most frustrating problems in syslog eventing and the most frustrating in analytics. For far too long the choices have been to use the devices name OR use reverse DNS but never both. Today SC4S 1.20.0 solves this problem by doing what you would do!

  1. If the device has a host name in the event use that
  2. Else if our management/cmdb solution knows the right name use that instead
  3. Else maybe someone updated DNS try that instead.

Simple logical easy to understand and available now in Splunk Connect for Syslog. No more of this

Event with IP as a host

Plenty more like this

IP translated to host using CMDB sourced lookup