> 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/integrations/snyk-ide-plugins-and-extensions/snyk-language-server/ide-and-cli-usage-telemetry.md).

# IDE and CLI usage telemetry

How the Snyk Language Server collects usage telemetry after each successful test

Snyk Language Server collects usage telemetry after each successful test, through the Snyk proprietary Analytics service. Data does not pass through any third-party services.

The request body contains several categories of data:

* **Versions and types of integration**, for example, Language Server version, IDE type and version, plugin type and version
* **Local environment**: OS, architecture
* **Project data**, for example, repository git URL, branch name
* **Performance data**: duration of the scan in milliseconds
* **Event details**, for example, event type, timestamp, status, number of findings

The API path contains a unique Snyk Organization ID. Thus, data is annotated with Organization information.

Personally identifiable information (PII) for users is not part of the request. The Snyk internal analytics service API requires an authentication token to be present. Incoming event data is merged with user data inside the backend service, to allow Snyk to build a special report page: [Developer IDE and CLI usage](https://docs.snyk.io/scan-fix-and-prevent/prevent/analytics/reports-tab/prevention-reports#developer-ide-and-cli-usage-report).

You can see the open-source logic and examine it directly in the GitHub repository: [snyk/go-application-framework](https://github.com/snyk/go-application-framework/blob/main/internal/api/clients/analytics_v20240307.go). This is useful when a security audit is required.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snyk.io/developer-tools/integrations/snyk-ide-plugins-and-extensions/snyk-language-server/ide-and-cli-usage-telemetry.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.