Aggregate and display system metrics with anomaly detection for a time period
Install
npx skills add https://github.com/ruvnet/ruflo --skill observe-metricsSKILL.md
Observe Metrics
Aggregate counters, gauges, and histograms from the observability namespace and flag anomalies.
When to use
When you need a snapshot of system health -- task completion rates, error rates, active agent counts, memory usage, and token consumption. Useful for monitoring swarm performance and detecting degradation.
Steps
- Retrieve metrics -- call
mcp__plugin_ruflo-core_ruflo__memory_search --namespace observability(ormemory_list) to fetch metric records for the specified period (default: 1 hour). Thememory_*tool family routes by namespace;agentdb_hierarchical-*does NOT, so usememory_*here. - Aggregate -- compute:
- Counters: sum totals (tasks_completed, errors, token_usage)
- Gauges: current values (active_agents, memory_usage_bytes)
- Histograms: p50, p95, p99 (task_duration_ms, span_duration_ms)
- Compute baselines -- call
mcp__plugin_ruflo-core_ruflo__agentdb_pattern-search(ReasoningBank-routed; don't pass anamespaceargument — pattern-* tools ignore it) to establish baseline values for each metric. - Flag anomalies -- mark metrics deviating >2 standard deviations from baseline with direction (above/below) and severity
- Store patterns -- two paths (per ruflo-cost-tracker ADR-0001 dual-path pattern):
- Pattern store (typed, recommended):
mcp__plugin_ruflo-core_ruflo__agentdb_pattern-storewithtype: 'metric-snapshot'. No namespace arg. - Plain store (namespace-routable):
mcp__plugin_ruflo-core_ruflo__memory_store --namespace observabilityfor the snapshot tied to a timestamp.
- Pattern store (typed, recommended):
- Report -- display: metric name, current value, baseline, deviation, trend (up/down/stable), anomaly flag; overall health score (green/yellow/red)
CLI alternative
npx @claude-flow/cli@latest memory search --query "system metrics for last hour" --namespace observability
Related skills
azure-diagnosticsmicrosoft608KDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, troubleshoot functions, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, aazure-preparemicrosoft608KPrepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azazure-aimicrosoft608KUse for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.azure-deploymicrosoft607KExecute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: \"run azd up\", \"run azd deploy\", \"execute deployment\",