Use this page when an application should install standard observability exporters from one plugin configuration document instead of manually registering each subscriber.
The plugin kind is observability. It is registered by the core runtime, so
applications do not need to register a plugin implementation before validation
or initialization.
For plugin file discovery, precedence, merge behavior, editor controls, and gateway conflict rules, see Plugin Configuration Files.
Observability plugin configuration uses the generic NeMo Relay plugin document
shape, so field names are snake_case in every binding. This differs from
Node.js runtime classes such as OpenTelemetrySubscriber, which use
Node-native camelCase option names outside the plugin system.
Every exporter section is optional and defaults to disabled. A section is active
only when it includes enabled: true.
subscriber_name is not part of this config. The runtime infers
component-local subscriber names and registers them under the observability
plugin namespace:
__nemo_relay_plugin__observability__atof__nemo_relay_plugin__observability__atif__nemo_relay_plugin__observability__atif-{agent_scope_uuid}__nemo_relay_plugin__observability__opentelemetry__nemo_relay_plugin__observability__openinferenceplugins.toml ExampleInclude only the sections you want to configure. In layered plugins.toml
files, omission inherits lower-precedence values; write enabled = false to
disable an inherited section.
Validate plugin configuration before activating it. The plugin reports unsupported transports, unsupported ATOF modes, unsafe ATIF filename templates, unknown fields according to policy, and enabled exporters that are unavailable in the current build or target.
Call plugin.clear() or clear_plugin_configuration() during teardown.
Clearing the plugin config deregisters inferred subscribers, flushes file
exporters, and shuts down owned OTLP subscribers.
Use manual subscriber/exporter APIs instead of the plugin when you need custom subscriber names, explicit per-run exporter objects, or direct control over the collection window.