Installation

How to remove duplicate entries from Forwarder Deployments Monitoring Dashboard ?

hemantw7
Explorer

In Splunk monitoring console  Forwarders: Deployment panel has duplicate entries one is active with latest version and other old version as missing.

How i can remove old dated missing entries form host without building the forwarder asset table. 

Suggestions please?

sample :

hemantw7_0-1675450382558.png

 

Labels (1)
0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @hemantw7,

as @richgalloway and @isoutamo said, you could manually update the lookup but I'd avoid this.

Why don't you want to rebuild the forwarders asset table?

this feature is done just for solve your problem and to eliminate dismissed forwarders.

Ciao.

Giuseppe

0 Karma

richgalloway
SplunkTrust
SplunkTrust

You should be able to use the Lookup Editor app to modify the dmc_forwarder_assets.csv file.  Do so at your own risk.

---
If this reply helps you, Karma would be appreciated.
0 Karma

isoutamo
SplunkTrust
SplunkTrust

Have you done updates by removing old version and then install new one instead of updating that? This leads to generate a new GUID for that node which leads a duplicate entries with same node names. This coul also generate duplicate log events if/when you have lost the fishbucket db on UF.

Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Take Action Automatically on Splunk Alerts with Red Hat Ansible Automation Platform

 Are you ready to revolutionize your IT operations? As digital transformation accelerates, the demand for ...

Calling All Security Pros: Ready to Race Through Boston?

Hey Splunkers, .conf25 is heading to Boston and we’re kicking things off with something bold, competitive, and ...

Beyond Detection: How Splunk and Cisco Integrated Security Platforms Transform ...

Financial services organizations face an impossible equation: maintain 99.9% uptime for mission-critical ...