unknown_collector

Summary

{0}

Help

nanook ctl state lists configured collectors by name

Details

When this fires

Dispatch::pause / resume / trigger in nanook-admin/src/dispatch.rs got a name that doesn't correspond to any registered collector on this engine. Collector names are exactly what the plugin registers itself as, not the binary or the config section heading, so a typo or a stale runbook is the usual cause.

What to check

• Grab the live names from nanook ctl state (the collectors array) and reissue with the exact string (names are case-sensitive):

nanook ctl state
nanook ctl collectors pause cpu

• If the collector is missing entirely, check agent logs for plugin load errors and that the dylib lives where [plugins] points.