CTERA Portal Monitoring Service Configuration
  • 08 Nov 2022
  • 1 Minute to read
  • Dark
    Light
  • PDF

CTERA Portal Monitoring Service Configuration

  • Dark
    Light
  • PDF

Make sure port 443 outbound is open.

To check the connection between the CTERA Portal Monitoring Service and the CTERA Portal where the agent is installed. In the CTERA Portal Monitoring Service click image.png in the Instance list for the instance defined for the customer and choose Test connection from the menu. A popup window should display that the connection test was successful. If the CAUTION window is displayed, then you should check whether PostgreSQL is running on the CTERA Portal. If there is a problem with the credentials, then the CAUTION window is displayed prompting you to insert new credentials.

Adding pg_stat_statements to the CTERA Portal

The CTERA Portal Primary Server does not include the PostgreSQL pg_stat_statements extension. This extension is used by the CTERA Portal Monitoring Service to display statistics, such as:

  • Top returned rows
  • Top CPU time
  • Top I/O time

To install pg_stat_statements:

  1. Using SSH, log in as root to your CTERA Portal primary server.
  2. Change the user to postgres with the following command: su - postgres
  3. Access PostgreSQL with the following command: psql
  4. Run the following commands:
    CREATE EXTENSION pg_stat_statements;
    alter system set shared_preload_libraries = 'auto_explain','pg_stat_statements';
    
  5. Exit PostgreSQL by entering Ctrl+d
  6. Exit the postgres user by entering Ctrl+d
  7. Restart PostgreSQL with the following command: portal.sh restart_postgres
  8. Change the user to postgres with the following command: su - postgres
  9. Access PostgreSQL with the following command: psql
  10. Run the following commands:
    alter system set pg_stat_statements.max = 100000;
    alter system set pg_stat_statements.track = 'all';
    select pg_reload_conf();
    

Was this article helpful?