All skillsOperations · INSTRUCTION-ONLY Practice before you connect
Instrument a critical journey
Decide which logs, metrics, and traces will explain user-visible failures.
The workflow
When to use
Decide which logs, metrics, and traces will explain user-visible failures.
Workflow
- Trace the journey across components and define success and failure signals.
- Specify structured events, correlation IDs, latency metrics, and alert thresholds.
- Exclude secrets and unnecessary personal data; define retention and access.
- Describe an intentional test failure that proves each signal is useful.
Boundaries
Use only tools and data authorized for the task. Ask for missing requirements when they affect the result. Report what you verified and what you could not verify.
View and copy SKILL.md
SKILL.md
---
name: observability-plan
description: "Decide which logs, metrics, and traces will explain user-visible failures."
license: CC0-1.0
metadata:
author: "SI Editorial"
version: "1"
---
# Instrument a critical journey
## When to use
Decide which logs, metrics, and traces will explain user-visible failures.
## Workflow
1. Trace the journey across components and define success and failure signals.
2. Specify structured events, correlation IDs, latency metrics, and alert thresholds.
3. Exclude secrets and unnecessary personal data; define retention and access.
4. Describe an intentional test failure that proves each signal is useful.
## Boundaries
Use only tools and data authorized for the task. Ask for missing requirements when they affect the result. Report what you verified and what you could not verify.
## Try it
Instrument agent connection, tool calls, and credential revocation.
## Success looks like
A signal map with actionable alerts and privacy boundaries.
Try it with your agent
Instrument agent connection, tool calls, and credential revocation.
What a useful result looks like
A signal map with actionable alerts and privacy boundaries.