managing-middleware-io

name	managing-middleware-io
description	Use when working with Middleware Io — middleware.io full-stack observability platform for infrastructure monitoring, APM, log management, synthetic monitoring, and Kubernetes observability. Covers host metrics, application traces, log analysis, alert management, and dashboard review. Use when monitoring infrastructure health, investigating application performance, searching logs, or managing Middleware.io alerts.
connection_type	middleware-io
preload	false

Middleware.io Monitoring Skill

Query, analyze, and manage Middleware.io observability data using the Middleware.io API.

API Overview

Middleware.io uses a REST API at https://app.middleware.io/api/v1.

Core Helper Function

#!/bin/bash

mw_api() {
    local method="$1"
    local endpoint="$2"
    local data="${3:-}"
    if [ -n "$data" ]; then
        curl -s -X "$method" "${MIDDLEWARE_URL:-https://app.middleware.io}/api/v1/${endpoint}" \
            -H "Authorization: Bearer $MIDDLEWARE_API_KEY" \
            -H "Content-Type: application/json" \
            -d "$data"
    else
        curl -s -X "$method" "${MIDDLEWARE_URL:-https://app.middleware.io}/api/v1/${endpoint}" \
            -H "Authorization: Bearer $MIDDLEWARE_API_KEY"
    fi
}

MANDATORY: Discovery-First Pattern

Always discover hosts, services, and alert rules before querying.

Phase 1: Discovery

#!/bin/bash

echo "=== Infrastructure Hosts ==="
mw_api GET "hosts" | jq -r '.data[] | "\(.hostId)\t\(.hostname)\t\(.os)\t\(.status)"' | head -20

echo ""
echo "=== APM Services ==="
mw_api GET "apm/services" | jq -r '.data[] | "\(.serviceName)\t\(.language // "N/A")\t\(.status // "unknown")"' | head -20

echo ""
echo "=== Alert Rules ==="
mw_api GET "alerts/rules" | jq -r '.data[] | "\(.id)\t\(.name)\t\(.severity)\t\(.state)"' | head -15

echo ""
echo "=== Dashboards ==="
mw_api GET "dashboards" | jq -r '.data[] | "\(.id)\t\(.title)"' | head -15

Phase 2: Analysis

#!/bin/bash

echo "=== Host Metrics (CPU/Memory) ==="
mw_api GET "hosts/metrics?period=1h" \
    | jq -r '.data[] | "\(.hostname)\tcpu:\(.cpuPercent // 0)%\tmem:\(.memPercent // 0)%\tdisk:\(.diskPercent // 0)%"' | head -15

echo ""
echo "=== APM Service Performance ==="
mw_api GET "apm/services/metrics?period=1h" \
    | jq -r '.data[] | "\(.serviceName)\tp99:\(.p99Latency // 0)ms\terror_rate:\(.errorRate // 0)%\treqs:\(.requestCount // 0)"' \
    | sort -t$'\t' -k3 -rn | head -15

echo ""
echo "=== Recent Error Logs ==="
mw_api POST "logs/search" '{"query":"level:error","from":"now-1h","to":"now","limit":20}' \
    | jq -r '.data[] | "\(.timestamp[0:19])\t\(.service // "unknown")\t\(.message[0:80])"' | head -15

echo ""
echo "=== Active Alerts ==="
mw_api GET "alerts/active" | jq -r '.data[] | "\(.triggeredAt[0:19])\t\(.severity)\t\(.ruleName)\t\(.target)"' | head -10

Output Rules

• TOKEN EFFICIENCY: Target ≤50 lines — use period and limit parameters
• Use host-level and service-level aggregations before drilling down
• Filter logs at API level with query parameter

Output Format

Present results as a structured report:

Managing Middleware Io 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

Shortcut	Counter	Why
"I'll skip discovery and check known resources"	Always run Phase 1 discovery first	Resource names change, new resources appear — assumed names cause errors
"The user only asked for a quick check"	Follow the full discovery → analysis flow	Quick checks miss critical issues; structured analysis catches silent failures
"Default configuration is probably fine"	Audit configuration explicitly	Defaults often leave logging, security, and optimization features disabled
"Metrics aren't needed for this"	Always check relevant metrics when available	API/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 error	Assumed permission failures prevent useful investigation; actual errors are informative