A Complete And Easy Guide To Check Elasticsearch

To poll Elasticsearch db status, we usually need to learn and try many many REST API. When we’re new, it would take quite a while to put all the pieces together.

As Ops/DevOps, we are usually more concerned about cluster health and data inside. Enclosed is A Simple Step-By-Step Guide to check elasticsearch. Cluster, Nodes, Shards, Indices, Documents And Beyond.

The Complete Guide To Query And Check Elasticsearch


Generate Common DB Data Report By ELK

Usually critical data is stored in DB. We can periodically poll and combine key metrics from DB into a data report, such as how many tables/collections in DB, how many items in each critical table, etc. Data report enables people to visualize the history and trend of key metrics.

Furthermore if the basic data report can be generated automatically, people can easily add more metrics, which may make more business sense. The most exciting part is that we can get a general solution which applies to different projects! So how we can get this idea started?

DB History Report


Restart One Elasticsearch Instance From Jenkins

Have your ES instances even run into full gc? Then you have to restart it.

But how do you do that?

You want to play safe. A list of procedure to follow. Run, check and wait. Manually!

Once restarted, shards loading could take time. Maybe hours. You don’t enjoy checking it over and over again, do you?

Why not automate it via Jenkins? What’s better we can get versatile slack notifications.

Restart One Elasticsearch Instance From Jenkins