Metrics & Telemetry

Note

Enterprise Feature — Metrics & telemetry is available on superglue Enterprise plans. Contact us to learn more.

Superglue exposes organization-scoped runtime metrics via a Prometheus text exposition endpoint. Use these to build dashboards, SLOs, and alerts for your Superglue usage.

Endpoint

GET /v1/metrics

https://api.superglue.cloud/v1/metrics

Auth: Authorization: Bearer <SUPERGLUE_API_KEY>
Format: Prometheus text exposition (text/plain; version=0.0.4)

Note

OpenTelemetry users: Superglue exposes metrics in Prometheus format. To integrate with an OpenTelemetry stack, use an OpenTelemetry Collector Prometheus receiver and export via OTLP to your backend.

Quick Setup

Prometheus

Option A: Using authorization (recommended)

scrape_configs:
  - job_name: superglue
    scheme: https
    metrics_path: /v1/metrics
    static_configs:
      - targets: ["api.superglue.cloud"]
    authorization:
      type: Bearer
      credentials: "<SUPERGLUE_API_KEY>"

Option B: Using bearer_token

scrape_configs:
  - job_name: superglue
    scheme: https
    metrics_path: /v1/metrics
    static_configs:
      - targets: ["api.superglue.cloud"]
    bearer_token: "<SUPERGLUE_API_KEY>"
    # or: bearer_token_file: /etc/secrets/superglue_api_key

OpenTelemetry Collector

Configure the collector to scrape Superglue via the Prometheus receiver:

receivers:
  prometheus:
    config:
      scrape_configs:
        - job_name: superglue
          scheme: https
          metrics_path: /v1/metrics
          static_configs:
            - targets: ["api.superglue.cloud"]
          authorization:
            type: Bearer
            credentials: "<SUPERGLUE_API_KEY>"

exporters:
  otlp:
    endpoint: "<YOUR_OTLP_ENDPOINT>"

service:
  pipelines:
    metrics:
      receivers: [prometheus]
      exporters: [otlp]

Example Response

# HELP superglue_runs_total Total number of finished runs (org-scoped).
# TYPE superglue_runs_total counter
superglue_runs_total{status="success",source="api"} 12
superglue_runs_total{status="failed",source="scheduler"} 3

# HELP superglue_run_duration_seconds_p95 p95 run duration over a trailing window (org-scoped).
# TYPE superglue_run_duration_seconds_p95 gauge
superglue_run_duration_seconds_p95{source="frontend",window="300s"} 1.23

---

Metrics Reference

superglue_runs_total

Type: Counter

Total number of finished runs in your org, grouped by outcome and source.

Label	Values
status	success, failed, aborted
source	api, frontend, scheduler, mcp, tool-chain, webhook

Tip

Best used for rates and error ratios over time using increase() / rate().

PromQL Examples

Total throughput (5m):

sum(increase(superglue_runs_total[5m]))

Error rate (5m):

sum(increase(superglue_runs_total{status=~"failed|aborted"}[5m]))
/
clamp_min(sum(increase(superglue_runs_total[5m])), 1)

Breakdown by source:

sum by (source) (increase(superglue_runs_total[5m]))

superglue_run_duration_seconds_p95

Type: Gauge

p95 runtime (seconds) for finished runs over a trailing 5-minute window.

Label	Values
source	api, frontend, scheduler, mcp, tool-chain, webhook
window	300s

Tip

This is end-to-end latency as Superglue sees it. Good for catching tail latency regressions.

PromQL Examples

Alert when API runs get slow:

superglue_run_duration_seconds_p95{source="api"} > 10

Dashboard all sources:

superglue_run_duration_seconds_p95

---

Use Cases

1. Monitor Scheduled Jobs

   Track superglue_runs_total filtered by source="scheduler" to see successful vs failed runs over time.

   sum by (status) (increase(superglue_runs_total{source="scheduler"}[1h]))

2. Alert on Failures

   Set up alerts when scheduled runs fail — catch issues before they pile up.

   increase(superglue_runs_total{source="scheduler",status="failed"}[15m]) > 0

3. Investigate in Superglue

   When an alert fires, jump into the Superglue dashboard or query the REST API to fetch the latest runs and inspect stack traces.

   curl -H "Authorization: Bearer $SUPERGLUE_API_KEY" \
     "https://api.superglue.cloud/v1/runs?status=failed&limit=10"