network-collector status is showing down

AzaKing

Hi all,

Initially both anomaly-detection and network-collector were showing failed. After rebooting the MPE, anomaly-detection recovered, but network-collector remains in failed state.

We have reviewed logs on the server and cannot find anything obvious pointing to the cause. General connectivity appears fine, registration is healthy, and other plugins are operating normally.

Questions:

1. Has anyone seen network-collector remain failed while everything else is healthy?
2. Are there specific logs or locations we should focus on beyond the standard Platform Connect/UAMS logs?
3. Is this commonly linked to stale plugin packages, upgrade remnants, certificates, or backend service dependencies?
4. Is there a safe method to force redeploy/reinstall just the network-collector plugin?

Any pointers appreciated.

Many Thanks

fop

The network collector is showing as critical, not down. How's it doing for performance and RAM usage?
You can also check the collector health in the SaaS portal and optionally download logs, though sometimes I find it quicker to run the diags on the mpe/NC and look through those instead.