Referenced from SKILL.md
SKILL.mdView in source ↗
Source excerpt starting at line 184.SKILL.mdView in source ↗Counters, histograms, and gauges power the **Metrics** explorer, dashboard panels, and alerts — create them once and record throughout. Python examples: [logging patterns](./references/python/logging-patterns.md#custom-metrics). Rust: the `logfire` crate has its own counter/histogram/gauge functions (e.g. `logfire::u64_counter()`) and an `ExponentialHistogram` type in its `metrics` module — not yet written up in the [Rust reference](./references/rust/patterns.md), so pull the signatures from the crate's own rustdoc. JS/TS: `@pydantic/logfire-node` has no custom-metrics wrapper of its own — create instruments with the raw OpenTelemetry Metrics API (`@opentelemetry/api`'s `metrics.getMeter(...)`); Logfire ingests them like any other OTLP metric.
Source excerpt starting at line 283.- **JavaScript/TypeScript**: [patterns](./references/javascript/patterns.md) (log levels, spans, error handling, config) and [frameworks](./references/javascript/frameworks.md) (Node.js, Cloudflare Workers, Next.js, Deno setup)- **Rust**: [patterns](./references/rust/patterns.md) (macros, spans, tracing/log crate integration, async, shutdown)- **Infrastructure monitoring** (hosts, Docker, Kubernetes, databases, cloud metrics — no app code): the `logfire-infrastructure` skill
