logging-platform-selection

What problem does it solve?

Logging platform selection prevents expensive, slow migrations by helping teams choose a platform that matches their actual volume, queries, retention needs, and incident-response requirements.

Core Features & Use Cases

• Decision-matrix guidance: Applies the cost, latency, retention, and query-power axes to your specific constraints so the choice fits real workloads.
• Volume and architecture selection: Recommends platform type (managed vs self-hosted), tiering strategies, and what to keep queryable versus archive.
• Operational success criteria: Focuses on incident-response speed (time to first useful result and dashboard freshness) and on log-shipping failure modes (forwarder lag and drops).
• Structured-log compatibility checks: Helps ensure your log format (JSON vs plain text), schema dynamics, and high-cardinality fields won’t cause runaway indexing or slow queries.
• Related-work steering: Points you upstream to log discipline and downstream to monitoring/alerts so retention and query performance support alerting and verification.

Quick Start

Use the logging-platform-selection skill to recommend a logging platform and retention architecture based on your current GB/day, your top incident queries, and whether you need hot/warm/cold tiers.