Percona Alerting not enabled

I have installed PMM latest version 3 using the manual instructions.
According to the docs Percona Alerting should be enabled by default but it was not active.
I restarted the docker image with the environment variable PMM_ENABLE_ALERTING=true and it is still not active.

If I go into PMM Configuration | Advanced Settings, I can toggle the Percona Alerting option on (it is set to off) but the “Apply Changes” button at the bottom of the page is not available to be pressed.

Any ideas how I can fix this?

Hi, PMM now uses grafana alerting.

Are you sure you’ve answered the question?
According to the docs for PMM v3 Percona alerting enhances the Grafana alerting with things like alert rule templates and this enhancement should be on by default.

Can you share which version are you using? I just tried to reproduce it on 3.2.0 and everything works fine.

I have installed 3.2.0 on two servers using the manual instructions.
Both servers have the same issues:
Percona Alerting is not enabled - there is no rule template tab
The “Advanced settings” page cannot be updated - a no access icon appears when I hover over the “Apply changes” button.
I have enabled LDAP integration and my userid is an admin. I have also logged in as the local admin user and see the same issue.

Hello,
Can you provide the same instructions you have used to deploy PMM 3.2.0 so that I could try to reproduce the same issue? Thanks.

Hi Jaimes,

I converted your manual instructions into an ansible script that I enclose below. I have used it to create two servers. On both there is no tab for rule templates and I cannot change anything in advanced settings:


Install PMM Server with Docker - Percona Monitoring and Management

- name: "Create a network"
  become: true
  community.docker.docker_network:
    name: "pmm-network"

- name: "Pull the WatchTower docker image"
  become: true
  community.docker.docker_image:
    name: "percona/watchtower:latest"
    source: pull

- name: "Create a watchtower container"
  become: true
  community.docker.docker_container:
    state: started
    recreate: true
    detach: true
    restart_policy: "always"
    published_ports: 
      - 8080:8080
    networks:
      - name: "pmm-network"
    env:
      WATCHTOWER_HTTP_API_TOKEN: "{{ redacted }}"
      WATCHTOWER_HTTP_API_UPDATE: "1"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    name: "watchtower"
    image: "percona/watchtower:latest"

Docker volumes (recommended) - Percona Monitoring and Management

- name: "Pull the PMM docker image"
  become: true
  community.docker.docker_image:
    name: "percona/pmm-server:3"
    source: pull

- name: "Create a volume for the PMM data"
  become: true
  community.docker.docker_volume:
    name: "pmm-data"

- name: "Create a PMM container"
  become: true
  community.docker.docker_container:
    state: started
    recreate: true
    detach: true
    restart_policy: "always"
    published_ports: 
      - 443:8443
      - 80:8080
    env:
      PMM_WATCHTOWER_TOKEN: "{{ redacted }}"
      PMM_WATCHTOWER_HOST: "http://{{ redacted }}:8080"
      GF_SMTP_ENABLED: "true"
      GF_SMTP_HOST: "redacted"
      GF_SMTP_SKIP_VERIFY: "true"
      GF_SMTP_FROM_ADDRESS: "redacted"
      GF_SMTP_FROM_NAME: "redacted"
      GF_AUTH_LDAP_ENABLED: "true"
      GF_AUTH_LDAP_CONFIG_FILE: "/etc/grafana/ldap.toml"
      GF_AUTH_LDAP_ALLOW_SIGN_UP: "true"
    mounts:
      - source: "pmm-data"
        target: /srv
    networks:
      - name: "pmm-network"
    name: "pmm-server"
    image: "percona/pmm-server:3"

- name: "Wait for web ui to become available"
  uri:
    url: "https://localhost"
    return_content: yes
    validate_certs: no
    status_code:
      - 200
  until : uri_output is defined and uri_output.status is defined and uri_output.status == 200
  retries: 40
  delay : 15
  register: uri_output

- name: "Change the admin password"
  become: true
  community.docker.docker_container_exec:
    container: "pmm-server"
    tty: true
    argv:
      - /bin/bash
      - "-c"
      - "change-admin-password {{ redacted }}"
  register: pmm_password_changed

Got to the bottom of the issue:
I was accessing the web ui vi a reverse proxy server whose configuration was causing the issue. When I bypassed the reverse proxy server and accessed the web ui directly I could see the missing functionality.

2 Likes