Monitoring and Observability

Watch the replay of this webinar to learn about how Modernizing Medicine dealt with a lack of high availability in AWS with the help of Continuent Tungsten and/or sign up for one of our other upcoming use case webinars in this series.

Where are the logs for a Tungsten Cluster and which are the proper log files to monitor if I do a master role switch to another node?

Latency-sensitive applications running in Java sometimes experience unacceptable delays under heavy I/O load. This blog discusses why this problem occurs and what to do about it for applications running Tungsten Clustering for MySQL.

In this blog post we will discuss how to best integrate various Continuent-bundled cluster monitoring solutions with PagerDuty (pagerduty.com), a popular alerting service.

This post covers some standard Nagios checks that would keep your MySQL / MariaDB / Percona Server cluster nodes healthy.

A robust monitoring setup is essential for cluster health and viability - if your replicator goes offline and you do not know about it, then that Replica becomes effectively useless because it has stale data. This means keeping a close watch on the health of the MySQL / MariaDB / Percona Server database nodes from many perspectives, from ensuring sufficient disk space to testing that replication traffic is flowing.

Managing a single cluster takes time and attention, and handling multiple clusters spread out over many sites is even more demanding. Tungsten Clustering offers a graphical administration tool called the Tungsten Dashboard™ to help with your management burden. You are able to view, monitor and maintain all of your clusters all in one place.

In this blog post, we talk about what happened during an installation of the Tungsten Cluster into an environment with SELinux running and mis-configured.