Component Service Discovery
Last updated - 08 January, 2026
Service Component Discovery automates the identification and synchronization of service components within Dynamic Service Insights (DSI). This feature ensures that services remain aligned with their defined DataSources, minimizing manual configuration and improving accuracy in component-level visibility and aggregation.
It extends the Active Discovery (AD) framework to support Aggregated Data LogicModules. With this feature, you can enable multi-instance configurations and automate component detection for services—ensuring that component changes, such as additions or removals are continuously reflected in LogicMonitor’s service monitoring model.
When Aggregated Data is selected as the DataSource Type, a new toggle labeled Enable Component Discovery becomes available.
Enabling this toggle performs the following actions:
- Marks the DataSource as multi-instance.
- Enables Active Discovery.
- Adds a Component Discovery section, where you can define the following fields:
- Component Key — the property identifier for each component.
- Component Values — the list of components to define within the service.
Note: You can add a maximum of up to 10 components.
For more information on configuring a Datapoint using the Aggregate Collection Method, see Aggregate Data Collection Method.
Example Use Case
An organization monitors an e-commerce web service that has three logical parts:
- Frontend (web servers)
- Backend (API servers)
- Database (DB nodes)
Component Configuration in the Aggregated DataSource
In the Aggregated DataSource’s Component Discovery section, the user configures:
- Component Key:
app.type - Component Values:
frontend,backend,database
With Service Component Discovery enabled, LogicMonitor creates three component instances under the service, as the DataSource is configured with three component values.
LogicMonitor maps resources (or instances) into a component by checking the configured property key and value.
A resource or instance with app.type=frontend is included in the Frontend component.
A resource or instance with app.type=backend is included in the Backend component.
A resource or instance with app.type=database is included in the Database component.
So the Frontend component automatically contains all members where app.type=frontend.
For each component instance, LogicMonitor aggregates metrics only from the resources or instances that match that component’s property mapping.
Note: Service Component Discovery depends on the following two things:
- The component configuration in the Aggregated DataSource (component key and allowed values)
- The actual properties present on the resource or instance (for example, app.type=frontend)
If the property is missing or does not match the configured values, the resource or instance is not mapped into that component.
