Elastic Search Resource

Elasticsearch is an open source search and analytics engine built on top of Apache Lucene. It is designed to store, search and analyze large volumes of data quickly and efficiently. Elasticsearch allows you to index structured and unstructured data, offering advanced full-text search features such as relevance search, keyword matching, filtering, and result highlighting. Additionally, it supports powerful aggregations for data analysis, allowing you to gain valuable insights from your information. With its distributed, scalable architecture, Elasticsearch can be deployed across clusters to handle intensive workloads, providing high availability, fault tolerance, and optimized performance. It is widely used in a variety of use cases such as full-text search, log analysis, application monitoring, content personalization, and real-time data search. Elasticsearch has become a popular choice for companies looking for a robust and flexible solution for indexing and searching data at scale.

How to monitor Elastic Search on One Platform

1 – In the side menu, click on Services Hub



2 – In the SearchEngine category, click on the Elastic Search card



3 – You will be directed to the Elastic Search configuration form, fill in the fields



4 – If you want, you can configure automatic incident opening. In the Open automatic incident section, fill in the fields:

  • Severity -> Choose between “SEV-1 – Critical”, “SEV-2 – High”, “SEV-3 – Moderate”, “SEV-4 – Low”, “SEV-5 – Informational” or “Not Classified”;
  • Check Interval in seconds -> This is the interval at which checking will take place (this interval cannot be less than the number of failures x the Interval configured in the monitoring form;
  • Failures to open automatic incident -> It is the number of failures necessary to open the automatic incident;
  • Check Interval in seconds -> This is the interval in which checking will take place (this interval cannot be less than the number of hits x the Interval configured in the monitoring form;
  • Hits to close automatic incident -> It is the number of hits needed to close the automatic incident;
  • Responders -> These are the teams that will be notified if there are incidents in this monitoring, and you can add one or multiple teams;

If necessary, you can create a team by clicking + RESPONDER, you will be directed to the form

to create the team, then click on the buttonfor the new team to appear in the list

***Don’t forget to activate the Enable to set up automatic incidents opening toggle to save the automatic incident opening settings



5 – Click on CREATE MONITORING 

Elasticsearch is an open source search and analytics engine built on top of Apache Lucene. It is designed to store, search and analyze large volumes of data quickly and efficiently. Elasticsearch allows you to index structured and unstructured data, offering advanced full-text search features such as relevance search, keyword matching, filtering, and result highlighting. Additionally, it supports powerful aggregations for data analysis, allowing you to gain valuable insights from your information. With its distributed, scalable architecture, Elasticsearch can be deployed across clusters to handle intensive workloads, providing high availability, fault tolerance, and optimized performance. It is widely used in a variety of use cases such as full-text search, log analysis, application monitoring, content personalization, and real-time data search. Elasticsearch has become a popular choice for companies looking for a robust and flexible solution for indexing and searching data at scale.

How to monitor Elastic Search on One Platform

1 – In the side menu, click on Services Hub



2 – In the SearchEngine category, click on the Elastic Search card



3 – You will be directed to the Elastic Search configuration form, fill in the fields



4 – If you want, you can configure automatic incident opening. In the Open automatic incident section, fill in the fields:

  • Severity -> Choose between “SEV-1 – Critical”, “SEV-2 – High”, “SEV-3 – Moderate”, “SEV-4 – Low”, “SEV-5 – Informational” or “Not Classified”;
  • Check Interval in seconds -> This is the interval at which checking will take place (this interval cannot be less than the number of failures x the Interval configured in the monitoring form;
  • Failures to open automatic incident -> It is the number of failures necessary to open the automatic incident;
  • Check Interval in seconds -> This is the interval in which checking will take place (this interval cannot be less than the number of hits x the Interval configured in the monitoring form;
  • Hits to close automatic incident -> It is the number of hits needed to close the automatic incident;
  • Responders -> These are the teams that will be notified if there are incidents in this monitoring, and you can add one or multiple teams;

If necessary, you can create a team by clicking + RESPONDER, you will be directed to the form

to create the team, then click on the buttonfor the new team to appear in the list

***Don’t forget to activate the Enable to set up automatic incidents opening toggle to save the automatic incident opening settings



5 – Click on CREATE MONITORING