PrismaLens

Alertmanager alerts, investigated by your agent

One webhook in. Ranked causes and evidence out.

curl -fsSL https://prismalens.io/install.sh | sh

Then run pl up

Also

Set up the webhook → 
receivers:
  - name: prismalens
    webhook_configs:
      - url: http://127.0.0.1:6473/api/webhooks/prometheus
        send_resolved: true
        http_config:
          authorization:
            type: Bearer
            credentials_file: /home/you/.prismalens/PRISMALENS_WEBHOOK_SECRET_FILE

How do Alertmanager alerts reach your agent?

Add a webhook receiver to Alertmanager that points at PrismaLens, with the token from your first pl up as a bearer credential. An alert reaches a service through its service label. By default, critical and high alerts on a service then start an investigation by your coding agent.

Wired in four steps

  1. Start PrismaLens

    The first pl up writes the webhook token.

  2. Add the receiver

    Point a webhook receiver at it, with the token.

  3. Match the service

    The alert's service label equals a service name.

  4. Let it run

    By default, critical and high alerts start an investigation.

Questions, answered

Which alerts start an investigation?

By default, a critical or high alert on a service. Each service can change that, from always to never. An alert with no matching service starts no investigation.

Can Alertmanager run on another machine?

Yes. Start PrismaLens with pl up --host 0.0.0.0. Over plain HTTP the traffic crosses the network in clear, so do this only on a network you trust.

What if my machine is off?

The webhook needs PrismaLens running when the alert fires. Alertmanager sends again only with the next group notification, so write the incident yourself for anything you missed.

Can I test it without Alertmanager?

Yes. Post a sample alert with curl and the token. The alerts guide has the exact command.