Sign inGet started

Tools

The tools an Elastic engineer reaches for every week

Six tools in the order the work happens: plan the cluster, deploy it, model and parse your data, transform it, and diagnose what goes wrong. Free, and everything runs in your browser.

1Plan

Sizing calculator

Turn GB per day and retention into the exact cluster you need.

  • Nodes, disk and RAM per tier, hot to frozen
  • Which limit decided each tier: disk, shards or resilience
  • Every step of the arithmetic, shown
Open the calculatorRead: Elasticsearch Capacity Planning for Logging: A Worked Example

2Deploy

Ansible playbook generator

Describe your hosts and roles. Run one command. A secured stack comes up.

  • Elasticsearch, Kibana and Logstash, any number of VMs each
  • TLS, certificates and passwords set for you
  • A PASS or a plain fix for every step while it runs
Open the playbook generatorRead: Elasticsearch Node Roles and Cluster Topology for Production

3Model

Index template generator

Paste one document. Get the mapping, templates and ILM policy for it.

  • A type for every field, with the reason
  • Component templates, index template and ILM, ready to PUT
  • The 8.x and 9.x differences stated, including logsdb
Open the template generatorRead: Elasticsearch Mapping Design for Production: Types and Limits

4Parse

Grok and dissect generator

Paste a few log lines. Get the pattern that splits them into fields.

  • Dissect when the format allows it, grok when it must
  • ECS field names and a line-by-line preview
  • The ingest pipeline and the Logstash filter
Open the pattern generatorRead: Ingest Pipelines vs Logstash: Where to Parse Your Logs

5Transform

Ingest pipeline builder

Build a pipeline by clicking on the fields of a real document.

  • 24 processors, picked per field from a menu
  • Drag to reorder, drop a field onto an object to move it
  • PUT, curl and a _simulate request to prove it
Open the pipeline builderRead: Ingest Pipelines vs Logstash: Where to Parse Your Logs

6Diagnose

Paste your cluster output

Paste what the cluster printed. Get what is wrong, why, and the fix.

  • Allocation explain, health and _cat tables understood
  • Elasticsearch's own reason, quoted, for every stuck shard
  • A fix with your index and node names filled in
Open the analyzerRead: Fix Unassigned Shards in Elasticsearch with Allocation Explain