OTel collectors (Fleet Hub)
Overview
Section titled “Overview”Developer tools → OTel collectors (/fleet-hub) opens Fleet Hub. It lists the OpenTelemetry Collectors managed through Shield360’s OpAMP server: the collector Shield360 runs to receive your telemetry, and any other collector you run under an OpAMP supervisor pointed at the same server.
For each collector you can:
- see whether it is healthy, what version it runs and where;
- read the configuration it is actually running;
- push a configuration of its own to it, without a restart, or clear it again.
Who can see it
Section titled “Who can see it”| Permission | Allows | Held by |
|---|---|---|
fleet_hub.read (View the fleet) | The list and each collector’s detail page | Owners, administrators, analysts and the Security role |
fleet_hub.configure (Configure the fleet) | Saving or clearing a collector’s configuration | Owners and administrators |
Fleet Hub is part of the Developer module. It is not available in the public demo, which has no live collectors.
The collector list
Section titled “The collector list”The list shows one row per connected collector. Select a row to open it.
| Column | Comes from |
|---|---|
| ID | The collector’s OpAMP instance id |
| Name | service.name |
| Version | service.version |
| Operating System | os.type |
| Started At | When the collector started |
| Status | The health the collector reports, green when healthy and red otherwise |
| Host Architecture | host.arch |
Use the column menu in the header to show or hide columns.
A collector’s detail page
Section titled “A collector’s detail page”The top of the page shows the collector’s Version, Started At, Host Name and Health Status. When the collector is unhealthy, its last error is shown underneath.
Select Show more for every identifying and non-identifying attribute the collector reports, and the health of each of its components (receivers, processors, exporters and extensions) when it reports them.
Below that are two editors:
- Custom Configuration: the configuration Shield360 sends to this collector. You can edit it.
- Effective Configuration (readonly): the configuration the collector reports it is running.
If the collector cannot be loaded, the page says Collector unavailable, with the reason, Back to Fleet Hub and Try again. A collector that is not found may have disconnected, or it may be connected to another Shield360 instance.
Push a configuration to one collector
Section titled “Push a configuration to one collector”Go to Developer tools → OTel collectors and select the collector.
Write YAML in Custom Configuration. The supervisor merges what it receives over the collector’s own configuration file, so you only need the sections you want to change.
processors: batch: timeout: 5sSelect Save. The OpAMP server checks that the configuration is valid YAML and is a map of keys to values. If it is not, the save is refused and the reason is shown under Configuration validation failed. A valid configuration is stored for that collector and sent to it straight away. The page then reloads, so Effective Configuration shows what the collector applied.
To remove the collector’s own configuration, empty Custom Configuration and select Save. The collector then goes back to the fleet configuration if there is one, or else to its own configuration file.
Fleet configuration and per-collector configuration
Section titled “Fleet configuration and per-collector configuration”Shield360 also sends one fleet configuration to every collector. It is rendered from the ingest pipeline settings, such as redaction patterns, pricing and data retention. A collector with a custom configuration from Fleet Hub keeps that configuration instead of the fleet configuration until you clear it.
Every save is recorded in the audit log, and can trigger a management alert.