fleet

To audit oracle versions and health across multiple nodes, you can run a deep census that pings remote nodes with timeouts, collects version and activity data, and saves structured JSON for comparison. It parses contacts.json to enumerate targets automatically.

Network discovery for oracle topology mapping is the process of enumerating nodes and oracles from a contacts file, pinging remote hosts, and generating a map of your network structure. This identifies all active oracles and their relationships during maintenance workflows.

To track oracle inventory changes between maintenance windows, you can run a diff mode census that compares the current network state against the last saved structured JSON scan. This highlights version changes, activity shifts, and topology updates without exposing secrets.

Yes, you can monitor oracle network activity without exposing credentials by using a local-first discovery approach that parses contacts.json, inspects local repositories, and pings remote nodes with short timeouts while explicitly excluding secrets from the saved JSON output.

The best way to prepare for a coordinated oracle upgrade is to run a full fleet census in deep mode to identify outdated oracles, quantify upgrade impact, and produce an actionable inventory of installed skills and versions across all nodes.

Yes, oracle network discovery works without hardcoding node targets by parsing a local contacts.json file to dynamically enumerate nodes and oracles, ensuring the census adapts automatically as your network topology changes.