---
title: "Monitoring"
description: "Observability for TraceRTM services: metrics, logs, traces, and alerting"
---

# Monitoring

Monitoring ties production signals back to traceability so you can see when changes regress behavior and where to fix them.

## Overview

- Metrics: latency, error rate, throughput per service.
- Logs: structured, correlated with request IDs and trace IDs.
- Traces: end-to-end spans across API, worker, and integrations.
- Alerts: SLO-based, actionable, and mapped to owners/artifacts.

## Setup checklist

- Export Prometheus/OpenTelemetry metrics from API and workers.
- Ship structured JSON logs to your SIEM; include `request_id` and `artifact_id` where possible.
- Configure tracing (OTLP) to your collector (e.g., Jaeger, Tempo).
- Link monitors to deployments in TraceRTM with `monitors` relationships.

## What to monitor

- API: latency p95/p99, error rate, queue depth, DB latency.
- Worker: job duration, failures/retries, backlog size.
- Integrations: webhook success/failures, external API latency/errors.
- Infra: DB CPU/IO, Redis ops/sec, NATS message rates.

## Alerting guidelines

- Alert on symptoms (latency/error SLO breaches) not just causes.
- Include runbooks and owners in alerts.
- Throttle noisy alerts; group by service and severity.
- Record alerts against artifacts/deployments for postmortems.

- [Learn more about related topics](#)
- [View examples](#)
- [Check the API reference](#)
