ouyangbo/hermes-agent
1
0
Fork 0
Code Issues Pull Requests Actions 12 Packages Projects Releases Wiki Activity

fix(relay): clarify opt-in plugin layering

Browse Source 
Signed-off-by: Bryan Bednarski <bbednarski@nvidia.com>
This commit is contained in:
Bryan Bednarski
2026-08-11 11:29:43 -06:00
parent 2ce4f228fe
commit ad9fb060c5
3 changed files with 98 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/observability/relay-shared-metrics.md
+9 -4
View File
@@ -43,10 +43,15 @@ behalf.
Relay plugin activation is owned by the native runtime and remains explicitly
opt-in. Set `HERMES_NEMO_RELAY_PLUGINS_TOML` to a selected `plugins.toml` to
activate configured middleware, exporters, or dynamic plugins. When it is
unset, Hermes does not invoke Relay's plugin initializer or trigger Relay
plugin configuration discovery. Invalid explicit configuration is reported
and Hermes continues without native plugin activation.
activate configured middleware, exporters, or dynamic plugins. When the
variable is unset, Hermes does not invoke Relay's plugin initializer, so Relay
does not perform plugin configuration discovery or layering. When it is set
and the selected file loads successfully, Relay performs its normal static
`plugins.toml` discovery and layers the selected static configuration over the
discovered configuration. Dynamic `[[plugins.dynamic]]` records are loaded
from the selected file only. If the selected file cannot be loaded, Hermes
reports the error and does not invoke Relay initialization or fall back to
ambient discovery.
Hermes core owns one Relay host and one isolated Relay session scope per Hermes
session. Core lifecycle producers use