Prometheus, Alertmanager and Pushgateway

Technical Preview

Overview

A client-mode connector for a curated observability / ITSM slice of the Prometheus HTTP API, Pushgateway, and Alertmanager API:

Catalog connector event	Entity / path	Notes
GET query	`GET /api/v1/query?query=`	PromQL instant query; typically no auth
GET query_range	`GET /api/v1/query_range`	PromQL range (`start` / `end` / `step`)
GET targets	`GET /api/v1/targets`	Scrape targets smoke / discovery
POST Pushgateway metrics	`POST /metrics/job/{job}`	text/plain OpenMetrics / Prometheus exposition; BASE = Pushgateway :9091
GET Alertmanager alerts	`GET /api/v2/alerts`	Alertmanager API v2; BASE = Alertmanager :9093

Default BASE_ADDRESS is http://prometheus.example.com:9090 (replace with your Prometheus host). Topics use itsm/prometheus/<object>/<verb>.

Prometheus, Alertmanager, and Pushgateway are usually separate hosts/ports (:9090 / :9093 / :9091). Point BASE_ADDRESS at the matching host for each event, or deploy separate connector copies. For HTTPS reverse proxies set WITH USE_SSL "true". Do not put a trailing slash on BASE_ADDRESS.

Prefer Hub secrets when a reverse proxy requires Basic or Bearer. Public demo.promlabs.com and prometheus.demo.prometheus.io allow anonymous PromQL reads, but they do not expose a writable Pushgateway — status remains blocked until a Pushgateway (and preferably owned stack) smoke succeeds.

Basic Syntax

# Coreflux REST_API template — Prometheus / Alertmanager / Pushgateway curated slice
# Auth: none by default; optional Bearer/Basic via reverse proxy
# BASE_ADDRESS: http://prometheus.example.com:9090
# PushMetrics → Pushgateway :9091; ListAlerts → Alertmanager :9093

DEFINE ROUTE PrometheusRestApi WITH TYPE REST_API
    ADD REST_API_CONFIG
        WITH BASE_ADDRESS "http://prometheus.example.com:9090"
        WITH ENABLE_CLIENT "true"
        WITH USE_SSL "false"
        WITH REQUEST_TIMEOUT '60'
        WITH DEFAULT_CONTENT_TYPE "application/json"
    ADD EVENT Queryinstant
        WITH SOURCE_TOPIC "itsm/prometheus/query/instant"
        WITH DESTINATION_TOPIC "itsm/prometheus/query/instant/response"
        WITH METHOD "GET"
        WITH ENDPOINT "/api/v1/query?query={value.json.query}&time={value.json.time}"
        WITH HEADERS
            ADD "Accept" "application/json"
    ADD EVENT Queryrange
        WITH SOURCE_TOPIC "itsm/prometheus/query/range"
        WITH DESTINATION_TOPIC "itsm/prometheus/query/range/response"
        WITH METHOD "GET"
        WITH ENDPOINT "/api/v1/query_range?query={value.json.query}&start={value.json.start}&end={value.json.end}&step={value.json.step}"
        WITH HEADERS
            ADD "Accept" "application/json"
    ADD EVENT Listtargets
        WITH SOURCE_TOPIC "itsm/prometheus/targets/list"
        WITH DESTINATION_TOPIC "itsm/prometheus/targets/list/response"
        WITH METHOD "GET"
        WITH ENDPOINT "/api/v1/targets"
        WITH HEADERS
            ADD "Accept" "application/json"
    ADD EVENT Pushmetrics
        WITH SOURCE_TOPIC "itsm/prometheus/pushgateway/push"
        WITH DESTINATION_TOPIC "itsm/prometheus/pushgateway/push/response"
        WITH METHOD "POST"
        WITH ENDPOINT "/metrics/job/{value.json.job}"
        WITH HEADERS
            ADD "Accept" "application/json"
            ADD "Content-Type" "text/plain"
        WITH BODY "{payload}"
    ADD EVENT Listalerts
        WITH SOURCE_TOPIC "itsm/prometheus/alertmanager/alerts/list"
        WITH DESTINATION_TOPIC "itsm/prometheus/alertmanager/alerts/list/response"
        WITH METHOD "GET"
        WITH ENDPOINT "/api/v2/alerts"
        WITH HEADERS
            ADD "Accept" "application/json"

Events

Event	Method	Endpoint	Request topic	Response topic
Queryinstant	GET	`/api/v1/query?query=&time=`	`itsm/prometheus/query/instant`	`itsm/prometheus/query/instant/response`
Queryrange	GET	`/api/v1/query_range?query=&start=&end=&step=`	`itsm/prometheus/query/range`	`itsm/prometheus/query/range/response`
Listtargets	GET	`/api/v1/targets`	`itsm/prometheus/targets/list`	`itsm/prometheus/targets/list/response`
Pushmetrics	POST	`/metrics/job/{job}`	`itsm/prometheus/pushgateway/push`	`itsm/prometheus/pushgateway/push/response`
Listalerts	GET	`/api/v2/alerts`	`itsm/prometheus/alertmanager/alerts/list`	`itsm/prometheus/alertmanager/alerts/list/response`

Auth

None (default):

Most Prometheus installs expose /api/v1/* without auth on private networks.
Leave Authorization headers off for Queryinstant / Queryrange / Listtargets.

Bearer via reverse proxy (optional):

Terminate TLS + auth in nginx / Traefik / similar in front of Prometheus / Alertmanager / Pushgateway.
Pass token on the MQTT request payload:
- Authorization: Bearer {value.json.token}
Store the token in Hub secrets / GET SECRET "PROMETHEUS_TOKEN". Never commit real credentials.

Basic via reverse proxy (optional):

Configure WITH USERNAME / WITH PASSWORD GET SECRET "PROMETHEUS_PASSWORD" on REST_API_CONFIG.
Remove any Bearer headers from events.

Install

Copy PrometheusRestApi.lot into your broker examples / connectors folder (no ADD METADATA in the deployable file).
Set BASE_ADDRESS to your Prometheus URL (use https://… and WITH USE_SSL "true" when TLS terminates on the API host or proxy).
-addRoute the file (or paste into Hub).
For Pushgateway and Alertmanager, either change BASE and re-deploy, or keep separate connector copies with the matching BASE.
Subscribe to the /response topics; publish JSON to the request topics.

Hub template listing uses hub-metadata.lot (WITH STATUS "beta", icon, doclink) — keep that file separate from the deployable connector.

Example payloads

Instant query

{ "query": "up", "time": "" }

Range query

{
  "query": "rate(http_requests_total[5m])",
  "start": "2026-10-04T00:00:00Z",
  "end": "2026-10-04T01:00:00Z",
  "step": "1m"
}

List targets

{}

Pushgateway push — MQTT JSON must supply job; body {payload} is raw text/plain exposition (example metrics body):

# TYPE coreflux_smoke_gauge gauge
coreflux_smoke_gauge{instance="factory"} 1

List Alertmanager alerts (BASE = Alertmanager)

{}

Complementary surfaces (not client events here)

Surface	Role
Alertmanager webhook receiver	Inbound: Alertmanager `webhook_config` POSTs alert payloads to a Coreflux REST_API server connector or HTTP ingress
Remote write	Prometheus remote_write (protobuf/snappy) — different protocol; not this JSON/text HTTP slice
OpenMetrics	Exposition format used by Pushgateway bodies and scrapes

References

Suggested branches (Hugo pushes)

App package: feat/rest-api-route-prometheus-alertmanager-and-pushgateway
Docs: feat/docs-rest-api-prometheus-alertmanager-and-pushgateway

Quick Start

Coreflux MQTT Broker

LoT Language

Coreflux HUB

VS Code - LoT Notebooks

Coreflux Portal

Using AI with Coreflux

Product Updates

Prometheus, Alertmanager and Pushgateway

Overview

Basic Syntax

Events

Auth

Install

Example payloads

Complementary surfaces (not client events here)

References

Suggested branches (Hugo pushes)

​Overview

​Basic Syntax

​Events

​Auth

​Install

​Example payloads

​Complementary surfaces (not client events here)

​References

​Suggested branches (Hugo pushes)

Overview

Basic Syntax

Events

Auth

Install

Example payloads

Complementary surfaces (not client events here)

References

Suggested branches (Hugo pushes)