Skip to main content
Version: NG-3.2

Integration with O11ySource

OmniAgent acts as the core execution layer in vuSmartMaps, responsible for applying configurations, deploying probes, and managing data collection across all monitored hosts. While configurations are defined centrally through the O11ySource module, OmniAgent executes them locally, ensuring data is collected, monitored, and reported back to the platform in real time. This integration enables a streamlined, automated, and consistent observability experience across distributed environments.

OmniAgent Discovery Lifecycle​

  1. O11ySource configured with OmniAgent Managed mode
  2. Platform waits for OmniAgent heartbeat
  3. If agent not disovered → Source Instance shows Pending
  4. When heartbeat received → Configuration pushed
  5. Probe created → Status moves to Configured
  6. Data starts flowing → Data Reception shows Receiving Data

How the Integration Works​

  • Configuration Creation: Users define or update data collection configurations within the O11ySources page in vuSmartMaps.
  • Configuration Delivery: Once saved, these configurations are automatically delivered to the corresponding OmniAgent service on each host.
  • Execution: OmniAgent applies the configuration locally, deploys or updates probes, and initiates data collection as per the defined parameters.
  • Status Reporting: OmniAgent continuously reports probe health, configuration state, and data collection updates back to vuSmartMaps. These updates are visible under both the OmniAgent Management Console and the O11ySource > Source Instances tab.
  • Synchronization: Any configuration updates or deletions made in O11ySources are automatically reflected within OmniAgent configuration state, ensuring both remain synchronized.
note

If OmniAgent is not discovered on a configured host, the source remains Pending until discovery. Once OmniAgent is detected, the configuration is applied automatically, and data collection begins. If the OmniAgent is not discovered, first download the OmniAgent and then follow the OmniAgent installation guide.

Management Modes​

During configuration, users can define how each data source should be managed:

  • OmniAgent Managed: Automatically controlled by OmniAgent. Configurations are applied once the service is discovered and active on the host.
  • Manually Managed: The setup and configuration files are deployed manually on the host by the user.
  • Remote Collection: Data is gathered directly from remote systems without deploying OmniAgent locally.
info

The available management modes depend on the selected O11ySource. Only the supported modes appear during configuration. If OmniAgent is not installed, follow the OmniAgent installation steps.

Configuration Details​

For detailed steps on configuring O11ySources, including how to add, import, and manage data sources, refer to the working with O11ySources

This provides:

  • Step-by-step instructions for creating new data sources.
  • Details on importing and reviewing configurations.
  • Guidance on choosing between OmniAgent-managed, manual, and remote management modes.

FAQs​

What is OmniAgent's role in O11ySource integration?

OmniAgent acts as the execution layer for O11ySource configurations. It applies configurations locally, deploys or updates probes, manages data collection, and reports status back to vuSmartMaps.

What happens when an O11ySource is configured in OmniAgent Managed mode?

The platform waits for an OmniAgent heartbeat from the host. Once the agent is discovered, the configuration is automatically pushed, the probe is created, and the source instance moves from Pending to Configured.

Why does an O11ySource Source Instance remain in Pending status?

The Source Instance remains Pending when OmniAgent has not yet been discovered on the configured host. Once a heartbeat is received, the configuration is pushed automatically.

When does O11ySource show Receiving Data?

After OmniAgent is discovered, the configuration is applied and the required probe is created. When data starts flowing, the Source Instance displays Receiving Data.