Show HN: Grafana agent observability for Hermes Agent A developer released grafana-agento11y-hermes, an Apache-2.0 plugin that records LLM calls and tool executions from Hermes Agent as generations and emits OpenTelemetry traces and metrics to Grafana Cloud's AI Observability. The plugin, installable via pip and enabled by editing ~/.hermes/config.yaml, requires a Grafana Cloud account and a token from the setup page, with free tier sufficient. It also supports other agents like Claude, Codex, and Cursor via a URL-based setup. Grafana Agent Observability https://grafana.com/docs/grafana-cloud/machine-learning/ai-observability/ plugin for Hermes Agent https://github.com/NousResearch/hermes-agent . Records LLM calls and tool executions as generations and emits OTel traces + metrics. Paste this into Hermes or any Claude / Codex / Cursor / similar agent that can fetch URLs : Install and configure the Grafana Agent Observability plugin for me by following https://raw.githubusercontent.com/alexander-akhmetov/grafana-agento11y-hermes/main/llms.txt The agent will walk you through pip install, ~/.hermes/config.yaml , and the credentials from the Agent Observability setup page. It will also explain what conversation data flows by default and how to tune it before turning anything on. pip install grafana-agento11y-hermes Install into the same Python environment hermes runs from which hermes to check . Then enable the plugin in ~/.hermes/config.yaml : plugins: enabled: - agento11y Hermes's plugins enable CLI does not see pip-installed plugins yet. It only scans ~/.hermes/plugins/ and the bundled directory. Editing the YAML directly is the workaround. The package, the module, the entry-point key and the env vars were all renamed. - Reinstall: pip uninstall hermes-plugin-sigil pip install grafana-agento11y-hermes The uninstall is required. The new package has a different name, so pip installs it alongside the old one instead of replacing it, and both would register a plugin. - Change the key in ~/.hermes/config.yaml from sigil to agento11y . The old key no longer resolves, and hermes will not load the plugin without this. - Rename your SIGIL env vars to AGENTO11Y , keeping the suffix SIGIL ENDPOINT becomes AGENTO11Y ENDPOINT . The setup page in Configure below gives you a fresh block with the new names. The plugin still reads the old names for now and logs what to rename, so nothing breaks the moment you upgrade. The SDK itself ignores them, so this fallback goes away once the SDK is fixed. Everything comes from one page in your stack: https://