connectors_prometheus v1

Typed specification

Generated by the pinned ess generate --kind docs from adapters/prometheus/spec/ess. Structural validation establishes consistency; behaviour, storage and cross-record predicates remain implementation obligations.

The system as a graph

A command is accepted by the component that owns its context, emits the events one of its outcomes declares, and a dashed edge is a binding carrying an event into the next command. Design §9 begins one step earlier, at the actor who invokes the first command, and so does this graph: a solid edge out of an actor is a grant, and an actor drawn with no edge at all may invoke nothing — which is something the model says, not an arrow somebody forgot.

Bounded contexts

• connection (connectors_prometheus.connection) — The Prometheus local connection — its native configuration, the prometheus.bearer profile and the configured identity probe that proves a credential. Eight types, no entities, no views, no commands, no events, no errors and no actors.
• reads (connectors_prometheus.reads) — Prometheus-owned PromQL instant and range selections, their result kinds and series bounds. Four types, no entities, no views, no commands, no events, no errors and no actors.
• rules (connectors_prometheus.rules) — Prometheus-owned alerting and recording rules as rules.list returns them, one record per rule. Five types, no entities, no views, no commands, no events, no errors and no actors.

Components

A component is a unit of ownership, not a deployment. How many of each runs, and what each needs, is the topology.

The other pages

page	what is on it
connection	the connectors_prometheus.connection vocabulary: its types, entities, views, commands, events, errors and actors
reads	the connectors_prometheus.reads vocabulary: its types, entities, views, commands, events, errors and actors
rules	the connectors_prometheus.rules vocabulary: its types, entities, views, commands, events, errors and actors
Interactions	every binding, with what it guarantees and what happens when it fails
Type crossings	every conversion this system permits, and the reason someone gave for it
Topology	what each component needs in order to run

---

Generated from connectors_prometheus v1 · model digest 5a394966bc5849079b110e96a78cbdd0e0f71db4e76dbe085d6826e6c18c9495 · contract digest 22177c4cb3e3da2cd6b496730bb7ca9a9dd7a984bf2b2c26511d9911190f9968. Do not edit this file; change the specification and regenerate it with ess generate.