Skip to content

Activity Center

The Activity Center in ClusterControl is a centralized hub that provides a comprehensive overview of all system activities, events, and tasks. It consolidates critical information from alarms, jobs activity, and audit logs into a single, easy-to-navigate interface. This feature is designed to enhance visibility, streamline monitoring, and simplify troubleshooting by offering a unified view of what is happening within the database environment.

Alarms

Alarms indicate problems that could affect or degrade the cluster as a whole. Each alarm is categorized as:

  • Cluster.
  • Cluster recovery.
  • Database health.
  • Database performance.
  • Host.
  • Node.
  • Network.

Accessing the alarms in ClusterControl can go to the following:

  1. Click on Actions → Details, to get a detailed explanation of the problem, together with the recommended action (if available) to resolve the problem.

  2. An alarm can be acknowledged by clicking on Actions → Mute. When muted, no notification will be sent via email. However, an alarm cannot be deleted or dismissed.

  1. Check all the alarm through CLI

    s9s alarm --list --long
    
  2. Filter the alarms specific cluster.

    s9s alarm --cluster-id=<clusterID> --list
    
  3. Remove the alarm from CLI can be done by executing the following.

    s9s alarm --delete --alarm-id=<alarmId>
    

    The alarmId can be found from the list of alarm.

Jobs

Shows aggregated view of jobs that have been initiated and performed in a cluster by ClusterControl (e.g., promote replica, enable read-only, create/restore a backup, etc). Each job entry has a job title, job status, cluster name, the user who started the job, timestamp, and duration.

  1. Rollover on the Cluster entry will pop up a cluster information card summarizing the cluster status. Rollover on the When entry will pop up a tooltip containing the exact timestamp with timezone.

  2. Click on the Actions ** → ** Details to see the job specification and messages. Inside the Job details popup, you have the ability to see the full job definition sent to the controller service for that particular job by clicking on the jobSpecs under the job’s name. Underneath it is the full job messages in descending order (newer first) returned by the controller service. The Copy to clipboard button will copy the content of the job messages to the clipboard. The job messages are commonly the first thing to look for when troubleshooting an issue that is happening to a cluster. It is highly recommended to include the job messages when opening a support request from us.

  1. Check the history of the job

    s9s jobs  --list --long
    
  2. Dig the detailed logs of specific job

    s9s job --log --job-id=<value>
    

The job-id can be found in the point 1 from the list of job are appear.

This allows administrators to monitor the progress of ongoing tasks, review the history of completed jobs, and troubleshoot any failed operations. The Jobs Activity feature is particularly useful for ensuring that automated tasks are executed as expected and for auditing changes made to the database environment.

Audit Log

Shows records of ClusterControl’s events and changes:

  • User authentication, cloud credentials, database configuration, and users changes
  • CMON configuration changes and jobs
  • ClusterControl user management changes (Users and ACLs), operational reports

Each log entry has the activity, type of activity, user, hostname or IP address (from where the user comes from), the corresponding cluster name, and timestamp.

  1. In the ClusterControl UI, go to Activity Center → Audit Log, check the activity of the users.

The Audit Log is essential for maintaining accountability, ensuring security, and facilitating compliance with operational and regulatory standards.