> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/developer-tools/snyk-cli/snyk-cli-analytics.md).

# Snyk CLI analytics

How Snyk CLI analytics work and how to control them

To provide a reliable and feature-rich experience, our command-line interface (CLI) utilizes two types of analytics: [Essential Operational Analytics](#essential-operational-analytics) and [Optional Usage Analytics](#optional-usage-analytics). We believe in transparency, and this document explains what data is collected, why it's necessary, and the controls you have.

## Essential Operational Analytics

A core set of anonymized analytics data is essential for the basic operation and health of our services. This data is **always collected** and cannot be disabled, as turning it off would impair core functionalities and the reliability of the tool.

### What data is collected?

This stream collects anonymized, non-personal operational data. Key data points include command success/failure rates, execution times (latency), and other technical metadata.

### How is this data used?

This information is vital for:

* **Powering Core Features**: Providing you with essential reporting and service functionality directly within the product.
* **Service Health and Monitoring**: Allowing us to monitor for performance issues, troubleshoot degradations, and ensure the overall health and reliability of the CLI.
* **Internal Analytics**: Understanding how the tool is performing to make informed decisions for improvements.

This operational data is securely processed in Snowflake for reporting and Datadog for real-time monitoring and troubleshooting. We only send the necessary fields required for these specific purposes.

## Optional Usage Analytics

The second category is general usage analytics, which helps us understand broader usage patterns (for example the CLI command, version, or error codes). You have full control over this and can opt out at any time.

You can disable this optional analytics collection by using either of the following methods:

* Set the environment variable `SNYK_DISABLE_ANALYTICS=1`
* Run the Snyk config command `snyk config set disable-analytics=1`

Using either of these methods opts you out of the optional usage analytics. The essential operational analytics described above remain active to ensure service functionality and reliability.

\\


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.snyk.io/developer-tools/snyk-cli/snyk-cli-analytics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.