Skip to content

cloudthinker-ai/CloudSkills / skills/connections/managing-lightstep

managing-lightstep

Unverified

Use when working with Lightstep — lightstep (now ServiceNow Cloud Observability) platform for distributed tracing, service health monitoring, change intelligence, and SLOs. Covers querying traces, analyzing service performance, reviewing deployments, managing alert conditions, and SLO tracking. Use when investigating latency regressions, analyzing service dependencies, or managing observability configurations.

Lightstep Monitoring Skill

Query, analyze, and manage Lightstep observability data using the Lightstep API.

API Overview

Lightstep uses a REST API at https://api.lightstep.com.

Core Helper Function

#!/bin/bash

ls_api() {
    local method="$1"
    local endpoint="$2"
    local data="${3:-}"
    local org="$LIGHTSTEP_ORG"
    local project="$LIGHTSTEP_PROJECT"
    local url="https://api.lightstep.com/public/v0.2/${org}/projects/${project}/${endpoint}"
    if [ -n "$data" ]; then
        curl -s -X "$method" "$url" \
            -H "Authorization: Bearer $LIGHTSTEP_API_KEY" \
            -H "Content-Type: application/json" \
            -d "$data"
    else
        curl -s -X "$method" "$url" \
            -H "Authorization: Bearer $LIGHTSTEP_API_KEY"
    fi
}

MANDATORY: Discovery-First Pattern

Always discover services, streams, and conditions before querying.

Phase 1: Discovery

#!/bin/bash

echo "=== Services ==="
ls_api GET "services" | jq -r '.data[] | "\(.id)\t\(.attributes.name)"' | head -20

echo ""
echo "=== Streams (Saved Queries) ==="
ls_api GET "streams" | jq -r '.data[] | "\(.id)\t\(.attributes.name)\t\(.attributes.query)"' | head -20

echo ""
echo "=== Alert Conditions ==="
ls_api GET "conditions" | jq -r '.data[] | "\(.id)\t\(.attributes.name)\t\(.attributes.expression)"' | head -15

echo ""
echo "=== SLOs ==="
ls_api GET "slos" | jq -r '.data[] | "\(.id)\t\(.attributes.name)\t\(.attributes.objective_percentage)%"' | head -15

Phase 2: Analysis

#!/bin/bash
SERVICE="${1:?Service name required}"

echo "=== Service Health ==="
ls_api GET "services/${SERVICE}" | jq -r '.data.attributes | "Latency P50: \(.latency_p50 // "N/A")ms\nLatency P99: \(.latency_p99 // "N/A")ms\nError Rate: \(.error_rate // "N/A")%\nOps/sec: \(.ops_per_sec // "N/A")"'

echo ""
echo "=== Recent Exemplar Traces ==="
ls_api GET "stored-traces?filter=service%3D${SERVICE}&limit=10" \
    | jq -r '.data[] | "\(.attributes.start_time[0:19])\t\(.attributes.duration_micros/1000)ms\t\(.attributes.root_span_name)"' | head -10

echo ""
echo "=== Service Dependencies ==="
ls_api GET "services/${SERVICE}/dependencies" \
    | jq -r '.data[] | "\(.attributes.direction)\t\(.attributes.name)\t\(.attributes.ops_per_sec) ops/s"' | head -15

echo ""
echo "=== Firing Conditions ==="
ls_api GET "conditions" | jq -r '.data[] | select(.attributes.state == "firing") | "\(.id)\t\(.attributes.name)\t\(.attributes.expression)"' | head -10

Output Rules

  • TOKEN EFFICIENCY: Target ≤50 lines — use limit query params and head in output
  • Use service-level aggregations before drilling into traces
  • Check service health before querying individual spans

Output Format

Present results as a structured report:

Managing Lightstep Report
═════════════════════════
Resources discovered: [count]

Resource       Status    Key Metric    Issues
──────────────────────────────────────────────
[name]         [ok/warn] [value]       [findings]

Summary: [total] resources | [ok] healthy | [warn] warnings | [crit] critical
Action Items: [list of prioritized findings]

Target ≤50 lines of output. Use tables for multi-resource comparisons.

Anti-Hallucination Rules

  1. NEVER assume resource names — always discover via CLI/API in Phase 1 before referencing in Phase 2.
  2. NEVER fabricate metric names or dimensions — verify against the service documentation or --help output.
  3. NEVER mix CLI commands between service versions — confirm which version/API you are targeting.
  4. ALWAYS use the discovery → verify → analyze chain — every resource referenced must have been discovered first.
  5. ALWAYS handle empty results gracefully — an empty response is valid data, not an error to retry.

Counter-Rationalizations

ShortcutCounterWhy
"I'll skip discovery and check known resources"Always run Phase 1 discovery firstResource names change, new resources appear — assumed names cause errors
"The user only asked for a quick check"Follow the full discovery → analysis flowQuick checks miss critical issues; structured analysis catches silent failures
"Default configuration is probably fine"Audit configuration explicitlyDefaults often leave logging, security, and optimization features disabled
"Metrics aren't needed for this"Always check relevant metrics when availableAPI/CLI responses show current state; metrics reveal trends and intermittent issues
"I don't have access to that"Try the command and report the actual errorAssumed permission failures prevent useful investigation; actual errors are informative
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 318kUpdated Claude CodeCodexUnverifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 117kUpdated Claude CodeCodexUnverifiedInstall