# 'Monitoring stopped' error on Application Security pages

**URL:** <https://community.dynatrace.com/t/monitoring-stopped-error-on-application-security-pages/42719>\
**Category:** Troubleshooting\
**Tags:** application-security, appsec-vulnerabilities\
**Created:** [November 22, 2023, 10:40pm UTC](https://community.dynatrace.com/t/monitoring-stopped-error-on-application-security-pages/42719 "2023-11-22T22:40:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![TeoMoldovanu](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/teomoldovanu/32/38331_2.png) [@TeoMoldovanu](https://community.dynatrace.com/u/TeoMoldovanu)\
**Post date:** [November 22, 2023, 10:40pm UTC](https://community.dynatrace.com/t/monitoring-stopped-error-on-application-security-pages/42719/1 "2023-11-22T22:40:00Z")

</div>

See below for potential reasons why the monitoring status radar on Application Security pages shows&nbsp; **Monitoring stopped. Please check settings** &nbsp;on any of the pages below.

### `Monitoring stopped`&nbsp;on Security overview

- Application Security isn’t activated.
  - To activate Application Security, see&nbsp;[Get started with Application Security](https://docs.dynatrace.com/docs/platform-modules/application-security/get-started-with-application-security).

- Both Third-party Vulnerability Analytics and Code-level Vulnerability Analytics are disabled. Your environment is monitored when at least one of these features is enabled.
  - To enable Third-party Vulnerability Analytics, see&nbsp;[Enable Third-party Vulnerability Analytics](https://docs.dynatrace.com/docs/platform-modules/application-security/vulnerability-analytics/get-started-with-vulnerability-analytics#enable-tpva).
  - To enable Code-level Vulnerability Analytics, see&nbsp;[Enable Code-level Vulnerability Analytics](https://docs.dynatrace.com/docs/platform-modules/application-security/vulnerability-analytics/get-started-with-vulnerability-analytics#enable-clva).

- No supported technology for Third-party Vulnerability Analytics is enabled,&nbsp; **Global Java code-level vulnerability detection control** &nbsp;for Code-level Vulnerability Analytics is disabled, and no custom monitoring rules for code-level vulnerabilities are in place. Your environment is monitored when at least one of these requirements is met.
  - To enable technologies for Third-party Vulnerability Analytics, see&nbsp;[Control by technology](https://docs.dynatrace.com/docs/platform-modules/application-security/vulnerability-analytics/get-started-with-vulnerability-analytics#technology).
  - To enable&nbsp; **Global Java code-level vulnerability detection control** , see&nbsp;[Configure monitoring](https://docs.dynatrace.com/docs/platform-modules/application-security/vulnerability-analytics/get-started-with-vulnerability-analytics#config).
  - To set custom monitoring rules for code-level vulnerabilities, see&nbsp;[Monitoring rules - Code-level Vulnerability Analytics](https://docs.dynatrace.com/docs/platform-modules/application-security/vulnerability-analytics/code-level-vulnerabilities/define-monitoring-rules-clv).

### `Monitoring stopped`&nbsp;on Third-party vulnerabilities

- Application Security isn’t activated.
  - To activate Application Security, see&nbsp;[Get started with Application Security](https://docs.dynatrace.com/docs/platform-modules/application-security/get-started-with-application-security).

- Third-party Vulnerability Analytics is disabled.
  - To enable Third-party Vulnerability Analytics, see&nbsp;[Enable Third-party Vulnerability Analytics](https://docs.dynatrace.com/docs/platform-modules/application-security/vulnerability-analytics/get-started-with-vulnerability-analytics#enable-tpva).

- No supported technology for Third-party Vulnerability Analytics is enabled.
  - To enable technologies for Third-party Vulnerability Analytics, see&nbsp;[Control by technology](https://docs.dynatrace.com/docs/platform-modules/application-security/vulnerability-analytics/get-started-with-vulnerability-analytics#technology).

### `Monitoring stopped`&nbsp;on Code-level vulnerabilities

- Application Security isn’t activated.
  - To activate Application Security, see&nbsp;[Get started with Application Security](https://docs.dynatrace.com/docs/platform-modules/application-security/get-started-with-application-security).

- Code-level Vulnerability Analytics is disabled.
  - To enable Code-level Vulnerability Analytics, see&nbsp;[Enable Code-level Vulnerability Analytics](https://docs.dynatrace.com/docs/platform-modules/application-security/vulnerability-analytics/get-started-with-vulnerability-analytics#enable-clva).

- **Global Java code-level vulnerability detection control** &nbsp;for Code-level Vulnerability Analytics is disabled, and no custom monitoring rules for code-level vulnerabilities are in place. Your environment is monitored when at least one of these requirements is met.
  - To enable&nbsp; **Global Java code-level vulnerability detection control** , see&nbsp;[Configure monitoring](https://docs.dynatrace.com/docs/platform-modules/application-security/vulnerability-analytics/get-started-with-vulnerability-analytics#config).
  - To set custom monitoring rules for code-level vulnerabilities, see&nbsp;[Monitoring rules - Code-level Vulnerability Analytics](https://docs.dynatrace.com/docs/platform-modules/application-security/vulnerability-analytics/code-level-vulnerabilities/define-monitoring-rules-clv).