skills.rest
ohsonerdy
ohsonerdyCOMMUNITY
Explore all skills by this author →
GitHub

logging-platform-selection

Select logging platforms and migration strategies using cost, latency, retention, and query-power constraints.

Updated Aug 23, 2026
Search Tags:#observability#ELK#Loki#Datadog#incident-response#logging-platform#log-retention
One-click install
npx skills add https://github.com/ohsonerdy/openclaw-frontier-stack --skill logging-platform-selection
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: logging-platform-selection
Source: https://github.com/ohsonerdy/openclaw-frontier-stack/tree/main/skills/logging-platform-selection
Command: npx skills add https://github.com/ohsonerdy/openclaw-frontier-stack --skill logging-platform-selection

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about logging-platform-selection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose a logging platform that fits my workload and budget?▼

Choosing a logging platform requires evaluating cost, latency, retention, and query power against your actual GB/day volume. This approach recommends a platform and tiered retention strategy that matches real workloads to prevent expensive, slow migrations.

ELK vs Loki vs Datadog: what is the best way to compare logging platforms?▼

Comparing logging platforms like ELK, Loki, and Datadog involves mapping your top incident queries and volume bands against a four-axis decision matrix. This method produces requirements-based recommendations that fit specific cost and query-power constraints.

How do I set up tiered log retention for hot, warm, and cold storage?▼

Tiered log retention separates what stays queryable from what gets archived based on your incident-response speed requirements. This strategy recommends keeping hot data for immediate dashboard freshness while archiving cold logs to control costs.

Do high-cardinality fields and JSON schemas cause slow log queries in OpenSearch?▼

High-cardinality fields and dynamic JSON schemas can cause runaway indexing and slow log queries in platforms like OpenSearch. Structured-log compatibility checks ensure your log format won't degrade incident-response speed or query performance.

When should I migrate from self-hosted ELK to a managed logging platform?▼

You should migrate from self-hosted ELK to a managed logging platform when cost-driven or incident-driven constraints exceed your current volume-band fit. This decision requires benchmarking time to first useful result and evaluating forwarder log-shipping failure modes.

Related Skills

Explore More Software Engineering Skills→
ricardoalt1515ricardoalt1515

logging-best-practices

Define structured logging best practices with correlation IDs and JSON formats.

Community
Advanced
kubiyabotkubiyabot
16

grafana

Manage Grafana dashboards, alerts, and data sources via the HTTP API.

Official
Intermediate
celticht32celticht32
4

couchbase-observability

Monitor Couchbase cluster health and configure Prometheus and Grafana alerts.

Community
Advanced
wesleyosantos91wesleyosantos91
6

finops

Analyze Terraform IaC and AWS configuration for recurring billing inefficiencies.

Community
Intermediate