# Radar stopped on DevSecOps Lifecycle Coverage with Snyk app

**URL:** <https://community.dynatrace.com/t/radar-stopped-on-devsecops-lifecycle-coverage-with-snyk-app/42728>\
**Category:** Troubleshooting\
**Tags:** snyk, devsecops, application-security, appsec-vulnerabilities\
**Created:** [November 21, 2023, 11:16am UTC](https://community.dynatrace.com/t/radar-stopped-on-devsecops-lifecycle-coverage-with-snyk-app/42728 "2023-11-21T11:16:50Z")\
**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 21, 2023, 11:16am UTC](https://community.dynatrace.com/t/radar-stopped-on-devsecops-lifecycle-coverage-with-snyk-app/42728/1 "2023-11-21T11:16:50Z")

</div>

**(Latest Dynatrace)**

A spinning radar on top of the&nbsp; **DevSecOps Lifecycle Coverage with Snyk** &nbsp;pages lets you know that

- Application Security is actively monitoring the coverage status of your running containers.
- Container image data from Snyk is available and recent.

When coverage analysis fails, the radar stops spinning and one of the following radar messages informs you of the problem.

- **Coverage data for container images currently unavailable**
  - Make sure your container images are&nbsp;[scanned by Snyk](https://dt-url.net/23034xd).
  - Make sure that an&nbsp;[outbound connection to Snyk is allowed](https://docs.dynatrace.com/docs/platform-modules/application-security/devsecops-lifecycle-coverage#outbound).
  - Make sure the&nbsp;[right permissions are enabled](https://docs.dynatrace.com/docs/platform-modules/application-security/devsecops-lifecycle-coverage#permissions).
  - In Workflows, check your&nbsp;[Snyk connection](https://docs.dynatrace.com/docs/platform-modules/application-security/troubleshoot#workflow)&nbsp;status or run the workflow manually. For details, see&nbsp;[Run a workflow](https://dt-url.net/q22349v). If the execution fails, edit your connection settings or set up a&nbsp;[new Snyk connection](https://docs.dynatrace.com/docs/platform-modules/application-security/devsecops-lifecycle-coverage#new-connection).

- **Coverage data for running containers currently unavailable**
  - [Enable Third-party Vulnerability Analytics](https://docs.dynatrace.com/docs/platform-modules/application-security/vulnerability-analytics/get-started-with-vulnerability-analytics#enable-tpva)&nbsp;globally.
  - Make sure that your&nbsp;[monitoring rules](https://docs.dynatrace.com/docs/platform-modules/application-security/vulnerability-analytics/third-party-vulnerabilities/define-monitoring-rules-tpv)&nbsp;don’t exclude any entities.

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

- **Coverage data for container images and running containers currently unavailable**
  - Go through all the suggestions above.
