Data collection
Elasticsearch
Cluster health, JVM heap, indices, search latency, indexing rate.
- Metrics
- Agentless
- Package 1.0.2
What it collects
- Signals
- Metrics
- How it collects
- Dedicated collector receiver (
elasticsearch) - Where it runs
- Agentless: your workspace's cloud gateway can run it, with nothing to install. Collectors you install can run it too.
- Discovery
- Found automatically on hosts and in Kubernetes, on port 9200
- Package version
- 1.0.2
Included in the package
- 52 workflow actions
How to connect it
- 01Open the connect wizardIn the Tracix console, open Integrations and pick Elasticsearch.
- 02Choose where it runsAgentless runs it on your workspace's cloud gateway. Pick a policy to run it on collectors you install.
- 03Fill in the connectionEnter the settings the wizard asks for. Collectors pick up the policy change on their own.
More in databases
All packages in databases
PostgreSQL
Databases
Vacuum stats, bloat, replication lag, query latency, lock contention.
Metrics
MySQL
Databases
Connection pool, replication lag, slow query rate, table growth.
Metrics
SQL Server
Databases
Batch and transaction rates, waits, locks, top queries and live query samples from Microsoft SQL Server.
Metrics
MongoDB
Databases
Replication, sharding, ops/sec, page faults, lock state.
Metrics
Redis
Databases
Memory usage, hit rate, replication, persistence, slowlog.
Metrics
Cassandra
Databases
Client request throughput and latency, pending compactions, storage load, read stage backlog, and JVM heap via Jolokia.
Metrics
Connect Elasticsearch to Tracix
Start free and connect it from the console, or book a demo and we will walk through your environment with you.