observability-conventions
Skill2 starsChanged 18 days agoMITView on GitHub
Distributed-tracing, logging, metrics, and alerting conventions for GeoAssets — context propagation, log/trace correlation, high-cardinality structured telemetry, vendor-agnostic instrumentation, SLO-based alerting, and tail-based sampling. Use when writing or reviewing code that emits logs/traces/metrics, touches GeoAssets.Infrastructure.Observability, crosses an async/queue boundary (Kafka, Service Bus, background Task), or when discussing alerting/sampling strategy.
In this repository12 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- code-gen-dagSkill
- outer-loop-dag-orchestratorSkill
- plan-gen-dagSkill
- solid-code-synthesizerSkill
- csharp-conventionsSkill
- jira-conventionsSkill
- outer-loop-dag-orchestratorSkill
- solid-code-synthesizerSkill
- ui-ux-pro-maxSkill
- solid-code-synthesizerSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Every entry records status: current (usable today, not gated by version) since observability practice here isn't tied to a language or …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Observability Conventions
Distilled, source-attributed engineering guidance — not a restatement of things you already know. Each reference file below traces back to a specific set of directives; when a claim turns out to be wrong or superseded, fix it at the source file, don't just override it in a conversation.
How this skill is organized
references/holds one file per topic. Read only the file relevant to the task at hand — don't load the whole set speculatively.- Every entry records status:
current(usable today, not gated by version) since observability practice here isn't tied to a language or runtime version the waycsharp-conventions'futureentries are. - Each file ends with a "Where this would apply in GeoAssets" section
grounding the directive in the actual state of
GeoAssets.Infrastructure.Observabilityand its call sites — treat those notes as a snapshot, not a guarantee; re-check the referenced file/line before relying on it, since the code moves.
References
| File | Topic | Status |
| context-propagation-and-causality.md | W3C traceparent/tracestate, deterministic propagation across threads/tasks/queues | current |
| unified-correlation-of-pillars.md | MDC/ambient context, mandatory trace_id/span_id/service.name/env on every log line | current |
| high-cardinality-structured-telemetry.md | High-cardinality span/log attributes, structured logging vs. string interpolation | current |
| semantic-vendor-agnostic-instrumentation.md | OpenTelemetry/ActivitySource over vendor SDKs, exporter config pushed to infrastructure | current |
| slo-based-alerting.md | Golden signals, error budgets, burn-rate alerting vs. raw resource thresholds | current |
| tail-based-sampling.md | Retain 100% of errors + P95+ latency, small % baseline; head-based vs. tail-based sampling | current |
| activitysource-native-otel-and-log-correlation.md | Native ActivitySource/Activity ↔ OTel concept mapping, zero-cost-when-unsampled pattern, AddException, Serilog vs. OTel ILogger bridge for log correlation | current |
As more directives or sources are added, list them here with topic and status so this table stays the single index of what's been curated.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

