<p data-pm-slice="1 1 []">Atomic data refers to the smallest meaningful units of telemetry collected by the system, such as individual SFP optical power levels in decibel-milliwatts (dBm), exact serial numbers, sub-card/blade operational states, and specific Management Information Base (MIB) interface counters.</p>

Atomic data refers to the smallest meaningful units of telemetry collected by the system, such as individual SFP optical power levels in decibel-milliwatts (dBm), exact serial numbers, sub-card/blade operational states, and specific Management Information Base (MIB) interface counters.

What is "atomic data collection" in Komodo Eye?

What is Komodo Eye and what is its primary purpose?

How does Komodo Eye differ from traditional IT monitoring tools like SolarWinds or Nagios?

What is the core deployment architecture of Komodo Eye?

Is desktop client software or an agent required to run Komodo Eye?

What web browsers are officially supported for Komodo Eye?

What are the three infrastructure asset classes defined in Komodo Eye?

How does pricing work for monitored assets in Komodo Eye?

What database engines power backend telemetry storage in Komodo Eye?

What is the default historical data retention period in Komodo Eye?

Why is a 5-year data lake critical for network operations?

What hardware specifications are required for a high-end Komodo Eye server installation?

Does Komodo Eye support High Availability (HA)?

How does Komodo Eye support NERC CIP regulatory compliance?

What are numeric data vs. semantic data in Komodo Eye?

What is the "Manager of Managers" concept in Komodo Eye?

What are SAIDI and SAIFI metrics in Komodo Eye?

What is the "Binary Blind Spot" in traditional network monitoring?

How does Komodo Eye overcome the Binary Blind Spot?

What target user personas are supported in Komodo Eye?

FAQ: Operations, Visibility & Basic Setup