Index of every page on this site: llms.txt
All skills
launchdarkly avatar

/alert-investigation

@f0ee110 official
Run it yourself

Investigates a firing or recently fired observability alert: finds the firing and replays the value it evaluated, decides whether the alert is chronic noise or a new problem, reuses any automatic investigation, then finds the cause (what changed, which host, version or route is over-represented) and returns a structured diagnosis with cause, scope and next steps.

Use this Skill: https://skilld.dev/gh/launchdarkly/ai-tooling/alert-investigation

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

errors.md

≈439 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Alert investigation: errors

Load this file for an error alert: error count or rate, a new error group, crash rate.

Before you look for a cause

  • Replay the firing from get-alert-firing-history, then with compareTo: "1w". An error count that was the same last week is a standing bug, not this firing's cause.
  • Name the groups. search-error-groups with the alert's query, the firing window and sort: "count"; for new-group alerts, sort: "first_seen".

Investigation shape

  1. Read the top group with get-error-group (secureId): stack, one occurrence, its trace_id and session. The originating frame is the deepest application frame, not framework code.
  2. Onset: search-aggregations with productType: "errors", the group's exception.message filter, over a window wider than the alert, bucketCount 24 to 48.
  3. What is over-represented: group by service_name, the version key and host.name with compareTo: "1d".
  4. What changed: get-changes for the service from 1 to 2 hours before the first occurrence. A version first seen just before it is the first suspect.
  5. Scope: sort: "sessions", or CountDistinct of secure_session_id with exact: true.

What goes in the diagnosis

  • What triggered: alert, threshold, value, and the error group secure IDs behind it.
  • Likely cause: the root frame, the trigger (version, flag, host), and one quoted error message.
  • Scope: occurrences, users or sessions, first-seen time.
  • Next steps: specific, such as "roll back version X" or "guard nil at handler.go:142".

Common mistakes

  • Citing a framework frame as the cause.
  • Filtering on event instead of exception.message.
  • Counting without a comparison window.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warningtoday3 checks · Risk SAFE
  • Gen Agent Trust Hubtoday

    The skill is designed to investigate observability alerts by querying a LaunchDarkly MCP server. It retrieves logs, traces, metrics, and session data to diagnose system failures. The primary security consideration is the ingestion of untrusted data from logs and error messages, which presents a surface for indirect prompt injection.

  • Sockettoday

    No alerts

  • Snyktoday

    Risk: MEDIUM · 2 issues

Signed by skilld at f0ee110. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 days ago
compatibility
Requires the remotely hosted LaunchDarkly MCP server
metadata
{
  "author": "launchdarkly",
  "version": "0.3.0"
}

README badge

README badge for launchdarkly/ai-tooling/alert-investigation