Newly installed Universal forwarders on windows servers are forwarding logs to Splunk Cloud but newly installed forwarders name is not coming up in forwarders list in Cloud Monitoring Console. What could be the reason?
While rebuilding forwarder database might sometimes help if it becomes corrupted or contains too many orphaned entries, the question worth looking into is how your UFs are deployed and configured. Are you sure they aren't sharing the GUID and hostname?
Hi @msatish
It looks like you need to "Rebuild Forwarder Assets". This can be done by going to Cloud Monitoring Console > Forwarders > Forwarder Monitoring Setup. and clicking on the "Rebuild Forwarder Assets" button.
I'd also recommend checking out the Review the Forwarder Monitoring Setup page docs which has more info about this and how to view/manage your forwarders via the CMC.
🌟 Did this answer help you? If so, please consider:
Your feedback encourages the volunteers in this community to continue contributing
You need to rebuild the forwarder asset table in the CMC for it to update properly.
Go to CMC > Forwarders > Forwarder Monitoring Setup > Rebuild Forwarder Assets
Refer the below docs:
Use the Forwarder dashboards - Splunk Documentation
Solved: monitoring console triggered alerts - missing forw... - Splunk Community
Solved: Why is our universal forwarder not visible in the ... - Splunk Community