Skip to content
Back to skills

Local Alerting

ASecurity

Upgrade a v0.1.46 dev env to local alert delivery — the compose `alertmanager`, the `alerts` evaluator workload and the alertmanager_port / alerts_port declaration, so forge.Alerts fire locally and reach forge.AlertReceivers and .forge/logs/<env>/alerts.log.

  • 10 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added November 13, 2026
developmentpythondockerapi

Works with

  • cli
  • api

Security analysis

A100/100

Scanned November 13, 2026

npx -y skills add reliant-labs/forge --skill local-alerting --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Local Alerting?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Local Alerting
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/reliant-labs-local-alerting/badge)](https://www.skillsdirectory.com/skills/reliant-labs-local-alerting)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: migration-v1.0.0-local-alerting
description: Upgrade a v0.1.46 dev env to local alert delivery — the compose `alertmanager`, the `alerts` evaluator workload and the alertmanager_port / alerts_port declaration, so forge.Alerts fire locally and reach forge.AlertReceivers and .forge/logs/<env>/alerts.log.
relevance: migration
---

# v1.0.0 — local alert delivery: an Alertmanager and an evaluator beside ClickStack

Use when `deploy/kcl/dev/main.k` declares `_observability` but no `alertmanager_port`.

## What changed

- `forge env up` now closes the alerting loop locally (`observability/alerts`, "Alerts fire locally too"):
  - an `alerts` host workload, `forge obs alerts run`, evaluates the env's rules continuously;
  - a compose `alertmanager` delivers what fires;
  - the Alertmanager's config is rendered by `forge/pkg/alerting/amconfig`, the control plane's own renderer.
- The default `reliant-inapp` receiver writes `.forge/logs/<env>/alerts.log`. More receivers are `forge.Alerts.receivers` (`forge.AlertReceiver`).
- `forge.Observability` gained `alertmanager_port` and `alerts_port`, which are declared together.
- A host workload whose `command` starts with `forge` now runs the forge that launched the env, not the one on PATH.
- `forge obs alerts check` and `forge obs profile` now reach the ClickStack in the compose project `forge env up` started (`forge-<id>-<env>`). Before, they named the default project and reported a running ClickStack as not running.

## Steps

1. In `docker-compose.yml`, copy the `alertmanager` service and the `alertmanager_data` volume from a fresh `forge project new`.
2. In `deploy/kcl/dev/main.k`, below `_profiles_otlp_port`:

   ```python
   _alertmanager_port = plugin.resolve_port("<project>-dev-alertmanager", 9093) if _observability and not _destination else 0
   _alerts_port = plugin.resolve_port("<project>-dev-alerts", 9095) if _observability and not _destination else 0
   ```

   Add `alertmanager_port = _alertmanager_port` and `alerts_port = _alerts_port` to `_observability_decl`.
3. In the same file, append two workloads to the no-destination branch of `_telemetry_workloads`: the `alertmanager` `forge.OnCompose` binding and the `alerts` host workload. Copy both from a fresh `forge project new`.

## Verify

`forge env up dev` prints `local alerting: N rule(s) → Alertmanager → reliant-inapp, …`, and its summary lists `alerts` and `alertmanager`. A rule that returns a row shows up in `curl -s localhost:<alertmanager port>/api/v2/alerts`, and in `.forge/logs/dev/alerts.log` once `group_wait` (30s) has passed.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in development →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.