FAQ
Common questions about how the Ozone Data Collector and the Ozone Orchestrator work together.
Does my data leave my network?
Only aggregated counts and enriched problems cross the boundary. The collector correlates raw events into deduplicated problems locally, then forwards just those results to the Orchestrator. Raw telemetry, device credentials, and packet-level data never leave your network.
What happens during an internet outage?
The collector keeps working. It continues collecting from and correlating your devices locally, buffers cloud-bound events using store and forward, and replays them once connectivity returns. Operator sessions on the appliance are validated offline, so you can keep using the local WebUI while the link is down. The only things that pause are fleet-wide visibility in the Orchestrator and over-the-air upgrades.
Which tier do I need for AI root-cause analysis?
LLM-based incident triage and root cause analysis are Enterprise only. Statistical anomaly detection and capacity forecasting are available in lower tiers, but the language-model RCA feature is gated to Enterprise.
How many devices can one collector monitor?
The limit is set by your license tier: 50 devices on Trial or Free, 250 on Professional, and unlimited on Enterprise.
Can I run multiple collectors or set up high availability?
Running multiple collectors and high-availability configurations are Enterprise features. Lower tiers run a single collector.
What protocols and platforms are supported?
The collector supports 63 onboarding methods across 10 categories, including SNMP v1/v2c/v3, SSH, Redfish, IPMI, WinRM, vSphere, Proxmox, Nutanix, the major clouds (AWS, Azure, GCP, OCI), Kubernetes, OpenShift, Docker, storage, wireless, load balancers, and firewalls. Separately, the collector can also ingest OT telemetry over industrial protocols such as Modbus and BACnet, which run as a runtime facility plugin rather than as add-a-device wizard methods. The full catalog is in Collection Methods.
How is data encrypted in transit?
The collector forwards to the Orchestrator over TLS on outbound TCP 443. On Enterprise, consolidated forwarding is additionally compressed and encrypted before it leaves the appliance.
How do I upgrade a collector?
Collectors upgrade over the air from the Orchestrator. You do not need to re-import an OVA or touch the appliance manually for routine upgrades.
How do I add an integration?
Integrations such as outbound notifications and ticketing are configured from the Orchestrator. See Integrations for the available connectors and setup steps.
Where does the collector store data, and how do I back it up?
The collector retains telemetry and state locally on the appliance. Backup and recovery guidance is in Persistence & Backup.
Do I need to expose the collector to the internet?
No. The collector dials out only and needs no inbound ports from the internet. The single requirement is outbound TCP 443 to the Orchestrator. See Firewall.
What ports does the collector listen on inside my LAN?
For passive telemetry it listens on the LAN for syslog (514/udp), SNMP traps (162/udp), NetFlow v5 (2055/udp), NetFlow v9 (9995/udp), IPFIX (4739/udp), sFlow (6343/udp), StatsD (8125/udp), and OTLP (4317/4318). The operator WebUI is on TCP 3000 on the LAN. These are internal only and are not exposed to the internet.
How do I get support?
Reach the TechForcz team through the channels listed on Support & Contact.