Redis Resource

Redis is an open source in-memory data storage system, widely used as a cache, key-value database, and messaging engine. It offers exceptionally fast performance because it keeps data in main memory instead of on disk. Redis supports a variety of data types, such as strings, hashes, lists, sets, and sorted sets, allowing for flexible data modeling. Additionally, it has advanced features including replication, disk persistence, distribution, and support for atomic operations. Redis is known for its simplicity, ease of use, and its ability to handle read- and write-intensive workloads. It is especially used in applications that require high speed, scalability, and low latency, such as dynamic data caching, message queuing, visitor counting, and real-time analytics.

How to monitor Redis on One Platform

 

1 – In the side menu, click on Services Hub

2 – In the Cache category, click on the Redis card

3 – You will be directed to the Redis 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 

Redis is an open source in-memory data storage system, widely used as a cache, key-value database, and messaging engine. It offers exceptionally fast performance because it keeps data in main memory instead of on disk. Redis supports a variety of data types, such as strings, hashes, lists, sets, and sorted sets, allowing for flexible data modeling. Additionally, it has advanced features including replication, disk persistence, distribution, and support for atomic operations. Redis is known for its simplicity, ease of use, and its ability to handle read- and write-intensive workloads. It is especially used in applications that require high speed, scalability, and low latency, such as dynamic data caching, message queuing, visitor counting, and real-time analytics.

How to monitor Redis on One Platform

 

1 – In the side menu, click on Services Hub

2 – In the Cache category, click on the Redis card

3 – You will be directed to the Redis 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