dip CLI sends to Azure Application
Insights. This page lists every event and every property it can send, so you can see exactly what
leaves your machine before you decide whether to keep it on.
What is never sent
A report never carries free text from dip. Every property is a value from a fixed list, a short label dip checks against a fixed pattern, a number,true or false, or a hash. dip never sends an error
message, a file path, a hostname, a tenant or app name, a file name, a token or an email address.
The one property whose text you choose is test_suite. If you set DIP_TELEMETRY_ENV, which marks
runs as tests, its value is sent exactly as you wrote it, so do not put anything there you would not
want sent. Test runs go to a separate test resource, unless APPLICATIONINSIGHTS_CONNECTION_STRING
is also set: that connection string sends every report, test or not, to the resource it names.
Two properties are hashes, and neither is a secret:
- Your tenant is sent as
workspace_hash, the first 16 hex characters of the SHA-256 hash of its hostname. The hash has no secret key, so anyone who knows or guesses your tenant’s hostname can compute the same value and match it. It keeps the hostname itself off the wire; it does not make your tenant anonymous. - A failure carries
error_fingerprint: a hash of the error message after dip replaces the parts it recognizes (quoted text, URLs, email addresses, file paths, hostnames and IP addresses, secret-shaped values and numbers). A word it does not recognize, such as an unquoted user name, stays in the text that is hashed. The hash has no secret key either, so someone who already has a candidate message can compute its fingerprint and compare. The fingerprint groups failures with the same cause; it does not contain the message.
Turn it off
Telemetry is on by default. Any one of these turns it off, and each wins overdip telemetry on:
dip telemetry status shows whether it is on, where it sends, and what is queued. See
dip telemetry in the command reference.
Events and properties
A report is one event. Each event carries the properties in Sent with every event, plus the ones listed under it. A property that has no value for a run is left out rather than sent empty. A value that does not fit its property’s list or pattern is sent asinvalid, never as the value itself.
Sent with every event
command_completed
A dip command returned normally.
command_aborted
A command stopped without finishing (it was killed, crashed or lost power). A later dip command reports it when it sends queued telemetry.
command_crashed
The command stopped on an internal error in dip.
cli_first_run
The first dip invocation for an installation.
No properties beyond the ones every event carries.
command_started
A dip command started. If it never finishes, a later dip command reports it as command_aborted when it sends queued telemetry.
No properties beyond the ones every event carries.
update_reexec
dip updated itself and is starting the new version to finish the command. The new run carries parent_session_id.
No properties beyond the ones every event carries.
login_completed
The interactive login flow ended.
update_checked
An update lookup completed.
update_applied
An attempt to install an update finished; outcome says whether it worked.
app_scaffolded
An app skeleton was created.
app_checked
dip app check finished.
app_built
A local single-platform app image build completed.
app_pushed
A multi-platform app image push completed, or failed on the way.
dev_started
A local development session started serving.
dev_stopped
A local development session stopped.
doctor_completed
dip doctor finished its checks.
skill_installed
The bundled coding-agent skills were installed.
mcp_installed
Your tenant’s MCP servers were registered with the coding agents on this machine.
request_completed
A network call dip made finished, after any retries.
request_retried
A network call failed and dip scheduled another attempt.
telemetry_dropped
dip discarded older queued telemetry because the queue on this machine was full.
The report around each event
Each event is sent as one Application Insights report. Besides the event’s name and the properties above, the report carries the time the event happened (UTC), the key of the Application Insights resource it is sent to (Altimate’s, or yours if you set your own connection string), and these tags:Related
Command reference
dip telemetry status, off and on.Using dip in CI
The environment variables dip reads in a pipeline.