# Percona Alerting not enabled **URL:** \ **Category:** PMM 3.x\ **Created:** [June 10, 2025, 10:56am UTC](https://forums.percona.com/t/percona-alerting-not-enabled/38265 "2025-06-10T10:56:39Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![SteveTelrock](https://avatars.discourse-cdn.com/v4/letter/s/22d042/32.png) [@SteveTelrock](https://forums.percona.com/u/SteveTelrock)\ **Post date:** [June 10, 2025, 10:56am UTC](https://forums.percona.com/t/percona-alerting-not-enabled/38265/1 "2025-06-10T10:56:39Z")
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? ---
**Author:** ![nurlan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/nurlan/32/1523_2.png) [@nurlan](https://forums.percona.com/u/nurlan)\ **Post date:** [June 10, 2025, 12:10pm UTC](https://forums.percona.com/t/percona-alerting-not-enabled/38265/2 "2025-06-10T12:10:44Z")
Hi, PMM now uses grafana alerting. ---
**Author:** ![SteveTelrock](https://avatars.discourse-cdn.com/v4/letter/s/22d042/32.png) [@SteveTelrock](https://forums.percona.com/u/SteveTelrock)\ **Post date:** [June 10, 2025, 1:08pm UTC](https://forums.percona.com/t/percona-alerting-not-enabled/38265/3 "2025-06-10T13:08:20Z")
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. > **[Percona Monitoring and Management - About Percona Alerting](https://docs.percona.com/percona-monitoring-and-management/3/alert/index.html)** > > Alerting notifies of important or unusual activity in your database environments so that you can identify and resolve problems quickly. When something needs your attention, Percona Alerting can be configured to automatically send you a notification... ---
**Author:** ![nurlan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/nurlan/32/1523_2.png) [@nurlan](https://forums.percona.com/u/nurlan)\ **Post date:** [June 11, 2025, 2:47pm UTC](https://forums.percona.com/t/percona-alerting-not-enabled/38265/4 "2025-06-11T14:47:43Z")
Can you share which version are you using? I just tried to reproduce it on 3.2.0 and everything works fine. ---
**Author:** ![SteveTelrock](https://avatars.discourse-cdn.com/v4/letter/s/22d042/32.png) [@SteveTelrock](https://forums.percona.com/u/SteveTelrock)\ **Post date:** [June 11, 2025, 2:55pm UTC](https://forums.percona.com/t/percona-alerting-not-enabled/38265/5 "2025-06-11T14:55:04Z")
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. ---
**Author:** ![jaimes](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/jaimes/32/20419_2.png) [@jaimes](https://forums.percona.com/u/jaimes)\ **Post date:** [June 18, 2025, 1:09pm UTC](https://forums.percona.com/t/percona-alerting-not-enabled/38265/6 "2025-06-18T13:09:43Z")
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. ---
**Author:** ![SteveTelrock](https://avatars.discourse-cdn.com/v4/letter/s/22d042/32.png) [@SteveTelrock](https://forums.percona.com/u/SteveTelrock)\ **Post date:** [June 24, 2025, 12:06pm UTC](https://forums.percona.com/t/percona-alerting-not-enabled/38265/7 "2025-06-24T12:06:05Z")
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](https://docs.percona.com/percona-monitoring-and-management/3/install-pmm/install-pmm-server/deployment-options/docker/index.html#install-pmm-server-watchtower) ``` - 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](https://docs.percona.com/percona-monitoring-and-management/3/install-pmm/install-pmm-server/deployment-options/docker/run_with_vol.html) ``` - 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 ``` ---
**Author:** ![SteveTelrock](https://avatars.discourse-cdn.com/v4/letter/s/22d042/32.png) [@SteveTelrock](https://forums.percona.com/u/SteveTelrock)\ **Post date:** [July 1, 2025, 8:08am UTC](https://forums.percona.com/t/percona-alerting-not-enabled/38265/8 "2025-07-01T08:08:42Z")
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.