Cassandra Resource

Cassandra is a highly scalable and highly available distributed database designed to handle large volumes of data distributed across multiple servers. Developed by Facebook and later released as open source software, Cassandra follows the columnar NoSQL database model. It provides high fault tolerance and no single points of failure, allowing data to be distributed across multiple machines and replicated to ensure redundancy and availability. Cassandra is optimized for fast writes and efficient read queries on large data sets, making it suitable for use cases that require high scalability, such as big data analytics applications, IoT, and real-time applications. With its distributed architecture and schema flexibility, Cassandra is a popular choice for companies that need to deal with data on a global, ever-growing scale.

How to monitor Cassandra on One Platform

1 – In the side menu, click on Services Hub


2 – In the Database category, click on the Cassandra card


3 – You will be directed to the Cassandra configuration page, 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 button  for 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 

Cassandra is a highly scalable and highly available distributed database designed to handle large volumes of data distributed across multiple servers. Developed by Facebook and later released as open source software, Cassandra follows the columnar NoSQL database model. It provides high fault tolerance and no single points of failure, allowing data to be distributed across multiple machines and replicated to ensure redundancy and availability. Cassandra is optimized for fast writes and efficient read queries on large data sets, making it suitable for use cases that require high scalability, such as big data analytics applications, IoT, and real-time applications. With its distributed architecture and schema flexibility, Cassandra is a popular choice for companies that need to deal with data on a global, ever-growing scale.

How to monitor Cassandra on One Platform

1 – In the side menu, click on Services Hub


2 – In the Database category, click on the Cassandra card


3 – You will be directed to the Cassandra configuration page, 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 button  for 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 

Experimente agora, grátis!