CodeQue

Get startedDocsRoadmapMissionPlayground

Telemetry

CodeQue VSCode extension and @codeque/eslint-plugin collects completely anonymous telemetry about products usage.

I use it to:

  • know how many unique users are there
  • know how many unique projects are served
  • know which query settings are most commonly used
  • capture exceptions

This helps me make better decision about project future.

Thank you for opting-in.

VSCode extension

Telemetry is implemented using @vscode/extension-telemetry

Besides default data collected by the package, it captured the following events

  • search finished
  • search error

It captures anonymous machine id and session id provided by VSCode.

It captures hash of the package.json

name
filed.

It captures query settings such as search mode or programming language.

It captures metrics like search time, search files count, results count.

It do not send your query nor search results.

How to opt out

You can opt-out by following the VSCode telemetry opt out instructions

ESLint plugin

Telemetry is implemented using applicationinsights

It only collects the custom events listed below, without capturing any other additional information.

Telemetry collects the following events

  • @codeque/eslint-plugin package installation
  • @codeque/warning eslint rule setup
  • @codeque/error eslint rule setup

It captures anonymous machine id generated using (node-machine-id)[https://www.npmjs.com/package/node-machine-id]

It captures whether eslint it's being run on CI server.

It captures hash of the package.json

name
filed.

It captures which parser is used.

It captures which search modes are used and how many queries are in the config.

It do not send queries, message or issues captured by set up rules.

How to opt out

You can opt-out by setting environment variable

CQ_ESLINT_TELEMETRY_DISABLE=true
in your path config or before running lint script.

To verify that telemetry is disabled, you can set environment variable

CODEQUE_DEBUG=true
and run your lint script.