Archive

After Update to Splunk Enterprise 6.2, why does the Deployment Monitor app shows duplicate forwarder entries in the "All Forwarders" view and falsely reports many missing forwarders?

Splunk Employee
Splunk Employee

After updating our search heads and Indexers to Splunk Enterprise 6.2, the Deployment Monitor app is reporting double the number of servers actually deployed in our environment. Duplicate entries are showing up as pre 4.2 and the Forwarder name is showing up with the IP address as well as those entries show up as missing

The 867 Universal Forwards that are reporting in properly are showing up with the FQDN's and show as active (they are correct).

Note that the 867 servers installed with UF's are all @ 6.1.X or higher for both Windows and Linux Universal Forwards

The Search heads and indexers were all reporting deployments properly prior to the 6.2 upgrade.

1 Solution

Splunk Employee
Splunk Employee

This issue has been identified as a product defect, with reference DEPMON-142.

In Splunk Enterprise 6.2, indexers are logging new events to metrics.log/group=tcpin_connections to record forwarder connection events, such as a connection closing:

11-13-2014 12:31:39.967 -0800 INFO  StatusMgr - destPort=9997, eventType=connect_close, group=tcpin_connections, sourceHost=10.140.126.97, sourceIp=10.140.126.97, sourcePort=54692, statusee=TcpInputProcessor

Unfortunately, the Deployment Monitor searches do not expect these events under group=tcpin_connections and only expect records reporting metrics, such as this one:

11-13-2014 12:33:14.272 -0800 INFO  Metrics - group=tcpin_connections, 127.0.1.1:33018:9997, connectionType=cooked, sourcePort=33018, sourceHost=127.0.1.1, sourceIp=127.0.1.1, destPort=9997, kb=10.08, _tcp_Bps=332.94, _tcp_KBps=0.33, _tcp_avg_thruput=0.14, _tcp_Kprocessed=354.89, _tcp_eps=0.42, _process_time_ms=1, old_evt_kBps=0.32, evt_misc_kBps=0.00, evt_raw_kBps=0.00, evt_fields_kBps=0.00, evt_fn_kBps=0.00, evt_fv_kBps=0.00, evt_fn_str_kBps=0.00, evt_fn_meta_dyn_kBps=0.00, evt_fn_meta_predef_kBps=0.00, evt_fn_meta_str_kBps=0.00, evt_fv_num_kBps=0.00, evt_fv_str_kBps=0.00, evt_fv_predef_kBps=0.00, evt_fv_offlen_kBps=0.00, build=149561, version=5.0.2, os=Linux, arch=x86_64, hostname=sosdev-ufwd-8, guid=EA1B8A53-350D-42D4-A08A-2670EC46208D, fwdType=uf, ssl=false, lastIndexer="10.140.48.33:9997,10.140.49.8:9997,127.0.1.1:9997", ack=true

This causes the logic of some searches in the Deployment Monitor app to fail, most notably those that list forwarders and/or attempt to detect missing forwarders.

The fix is simple and requires to re-scope the base search in the "forwarder_metrics" macro to always exclude the connection events and keep only the metric events.

There is a simple work-around, fortunately. Follow these steps, which assume that you have Deployment Monitor 5.0.3 installed:

  • Edit $SPLUNK_HOME/etc/apps/splunk_deployment_monitor/default/macros.conf

    • Find the definition of the "forwarder_metrics" macro on line 155 and change it like so: Before:

    index="_internal" source="metrics.lo" group=tcpin_connections | ...

After:

index="_internal" source="*metrics.lo*" group=tcpin_connections NOT eventType=* | ...
  • Restart Splunk or hit Splunk Web's .../debug/refresh endpoint to dynamically reload macro definitions

View solution in original post

Splunk Employee
Splunk Employee

This issue has been identified as a product defect, with reference DEPMON-142.

In Splunk Enterprise 6.2, indexers are logging new events to metrics.log/group=tcpin_connections to record forwarder connection events, such as a connection closing:

11-13-2014 12:31:39.967 -0800 INFO  StatusMgr - destPort=9997, eventType=connect_close, group=tcpin_connections, sourceHost=10.140.126.97, sourceIp=10.140.126.97, sourcePort=54692, statusee=TcpInputProcessor

Unfortunately, the Deployment Monitor searches do not expect these events under group=tcpin_connections and only expect records reporting metrics, such as this one:

11-13-2014 12:33:14.272 -0800 INFO  Metrics - group=tcpin_connections, 127.0.1.1:33018:9997, connectionType=cooked, sourcePort=33018, sourceHost=127.0.1.1, sourceIp=127.0.1.1, destPort=9997, kb=10.08, _tcp_Bps=332.94, _tcp_KBps=0.33, _tcp_avg_thruput=0.14, _tcp_Kprocessed=354.89, _tcp_eps=0.42, _process_time_ms=1, old_evt_kBps=0.32, evt_misc_kBps=0.00, evt_raw_kBps=0.00, evt_fields_kBps=0.00, evt_fn_kBps=0.00, evt_fv_kBps=0.00, evt_fn_str_kBps=0.00, evt_fn_meta_dyn_kBps=0.00, evt_fn_meta_predef_kBps=0.00, evt_fn_meta_str_kBps=0.00, evt_fv_num_kBps=0.00, evt_fv_str_kBps=0.00, evt_fv_predef_kBps=0.00, evt_fv_offlen_kBps=0.00, build=149561, version=5.0.2, os=Linux, arch=x86_64, hostname=sosdev-ufwd-8, guid=EA1B8A53-350D-42D4-A08A-2670EC46208D, fwdType=uf, ssl=false, lastIndexer="10.140.48.33:9997,10.140.49.8:9997,127.0.1.1:9997", ack=true

This causes the logic of some searches in the Deployment Monitor app to fail, most notably those that list forwarders and/or attempt to detect missing forwarders.

The fix is simple and requires to re-scope the base search in the "forwarder_metrics" macro to always exclude the connection events and keep only the metric events.

There is a simple work-around, fortunately. Follow these steps, which assume that you have Deployment Monitor 5.0.3 installed:

  • Edit $SPLUNK_HOME/etc/apps/splunk_deployment_monitor/default/macros.conf

    • Find the definition of the "forwarder_metrics" macro on line 155 and change it like so: Before:

    index="_internal" source="metrics.lo" group=tcpin_connections | ...

After:

index="_internal" source="*metrics.lo*" group=tcpin_connections NOT eventType=* | ...
  • Restart Splunk or hit Splunk Web's .../debug/refresh endpoint to dynamically reload macro definitions

View solution in original post

Splunk Employee
Splunk Employee

DEPMON-142 has been fixed as of Deployment Monitor 5.0.4 which is currently available for download

0 Karma

Explorer

Hi,

after upgrading from 6.1.1 to 6.3.1, we see the same problem. Search head is reporting ALL forwarders as IP, in the 'Splunk Alert: DM missing forwarders'-notification, as well in Forwarder overview in the Deployment Monitor - along with actual missing forwarders, being reported with FQDN.

Is the above mention workaround still the solution, or should the problem have been fixed? I tried to search for DEPMON-142 in the documentation site, but nothing seems to be found 😞

Regards
Claus

0 Karma

Splunk Employee
Splunk Employee

I recommend switching from Deployment Monitor to Splunk on Splunk (S.o.S.). There are no current plans for a new DepMon release. S.o.S. is actively and lovingly maintained/updated by our Support Team. The reporting and monitoring capability in S.o.S. is really top-notch.