Kevin

Plugin Architecture

Self-describing plugin manifests + lifecycle.

Plugin Architecture (v2026-08-02T101544Z-ab2bbdebf5) 2026-08-01 | Self-describing plugin manifests + lifecycle. 1 - Alertmanager Configuration alertmanager.yml global templates route receivers inhibit_rules 2 - Local Broker Bridge Config BRIDGE-CONFIG-LOCAL-BROKERS.md emqx.conf deploy order agents' tasks failure modes 3 - Docker Compose Strategy docker-compose.yml services networks volumes docker-compose.orion.yml overrides for Orion docker-compose.og2.yml overrides for OG2 docker-compose.vera.yml overrides for Vera 1. Configure Alertmanager with globa… 2. Define alert templates and routin… 3. Set up local broker bridges in em… 4. Deploy services using docker-comp… 5. Verify bridge connections and mes… Alertmanager Global Configuration global: resolve_timeout: 5m slack_api_url: '${SLACK_WEBHOOK_URL}' EMQX Bridge Configuration Snippet bridges.mqtt.to_vera { enable = true server = "ssl://bus.iiiai.us:8883" username = "<MACHINE>-cld" password = "<from .env.vera BUS_<MACHINE>_PASSWORD>" clientid = "<MACHINE>-bridge" } Alertmanager configuration is self-contained in alertmanager.yml. Local broker bridge configurations are documented in BRIDGE-CONFIG-LOCAL-BROKERS.md. Legend actor = initiates work · process = code path · store = state on disk · bus = durable queue · dashed = separate process cyan = request flow · pink = state read/write · dashed green = pull / return path · red = refusal

Provenance

This drawing is generated, not drawn. It is rebuilt from the source files below, so when they change the picture changes — a diagram here cannot quietly describe a system that no longer works this way.

Owner
Kevin
Slug
plugin-architecture
Rendered
2026-08-02T101544Z
From commit
ab2bbdebf5
Watches
3 paths
  • plugins
  • daemon/docs/PLUGIN_ARCHITECTURE.md
  • daemon/docs/PLUGIN.md