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.

logs.md

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

Alert investigation: logs

Load this file for a log alert: a log count or rate threshold, an error-log spike, a message pattern.

Before you look for a cause

  • Replay the firing from get-alert-firing-history, then with compareTo: "1w".
  • Group the matching logs with search-log-patterns using the alert's query and the firing window. The top two or three templates usually are the alert. If one template is a known, harmless message, the alert's query needs an exclusion.

Investigation shape

  1. Templates with counts: search-log-patterns with environments and the whole service family in services (get-keys, key: "service_name", search: "<svc>"), widening a service_name clause in the alert's query to the family; add patternKeys: ["service_name", "message"] to see whether one service or all of them log it. Do not filter to only the alert's service here: a single-service services makes every template look like one service and hides a failure shared across them.
  2. Where: search-aggregations with productType: "logs", environments and the service family in services, widening a service_name clause in the alert's query to the family (or dropping it), grouped by host.name, service_name or the version key, with compareTo: "1d". A failure logged by every service on one host points at the host.
  3. Verbatim evidence: search-logs for two or three examples, with environments and services, with fields to keep rows small. Follow a line's trace_id into get-trace.
  4. What changed: get-changes for the service.

What goes in the diagnosis

  • What triggered: alert, threshold, replayed value.
  • Likely cause: the template with its count, one verbatim line with timestamp and host, and the trigger.
  • Scope: services, hosts and requests affected.
  • Next steps: the fix, or an alert query change.

Common mistakes

  • Paging search-logs to count. Use search-log-patterns.
  • Paraphrasing log lines. Quote them.
  • Filtering on an unchecked key; a bad clause is dropped silently.

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