forked from asispts/neo-git-graph
-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathtelemetry.json
More file actions
59 lines (59 loc) · 5.5 KB
/
Copy pathtelemetry.json
File metadata and controls
59 lines (59 loc) · 5.5 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
{
"activate": {
"owner": "PlohnenSoftware",
"comment": "Sent once per session when the extension activates. Establishes the denominator that feature events are measured against, and records which settings diverge from their defaults so unused settings can be identified and removed.",
"settingsChanged": {
"classification": "SystemMetaData",
"purpose": "FeatureInsight",
"comment": "How many git-graph-libre settings the user has explicitly set. A count only."
},
"language": {
"classification": "SystemMetaData",
"purpose": "FeatureInsight",
"comment": "The display language Visual Studio Code is running in, for example 'en', 'pl' or 'de'. A language identifier only - it says which language the interface is in, not who is using it."
},
"translation": {
"classification": "SystemMetaData",
"purpose": "FeatureInsight",
"comment": "Which of this extension's translations actually served that session, for example 'en' when the display language is 'de' and no German translation exists. The pair of properties is what makes them useful: a difference between them is a request for a language this extension does not ship yet."
},
"setting.<name>": {
"classification": "SystemMetaData",
"purpose": "FeatureInsight",
"comment": "One boolean per setting the user has explicitly set, keyed by the setting's own name (for example 'setting.repository.showRemotes'). Records only THAT a setting was changed, never what it was changed to - several settings hold user-supplied strings (customBranchGlobPatterns can contain branch-name fragments, graphColors is free-form), so values are deliberately never sent. Used to find settings nobody uses."
}
},
"feature": {
"owner": "PlohnenSoftware",
"comment": "Sent when a command or context-menu action runs. Used to rank features by how many installations use them, so development effort goes where it is used, and to spot actions that fail often.",
"feature": {
"classification": "SystemMetaData",
"purpose": "FeatureInsight",
"comment": "The identifier of the action that ran, for example 'pushTag' or 'git-graph-libre.view'. This is a fixed identifier from the extension's own command list; no user content, path, or repository detail is included. Identifiers beginning with 'view.' are features that consist of something being shown rather than something being invoked - 'view.includeReflog' and 'view.includeUnreachableCommits' when recovered history was actually included in the graph, 'view.signedTagBadge' when a signed tag was there to badge, 'view.submoduleRepo' when a discovered Git submodule was listed in the repository dropdown, 'view.submoduleRepoActive' when the graph was actually drawn for one, 'view.uncommittedDetails' when the uncommitted-changes staging panel was opened, 'view.uncommittedTree' when that panel actually grouped changes into folders, 'view.stashRows' when a stash row appeared in the graph, and 'view.engineBackend' when the built-in Rust engine actually served a repository read. The two submodule identifiers are the presence of the feature only: the repository paths that decide them are compared inside the extension and are never sent, so neither identifier says anything about which repositories or submodules exist. Those are recorded at most once per session, not once per refresh."
},
"ok": {
"classification": "SystemMetaData",
"purpose": "FeatureInsight",
"comment": "Whether the action completed without throwing. The error message itself is not sent."
}
},
"common": {
"comment": "Visual Studio Code injects a fixed set of common properties into every event above: extension name and version, VS Code version, commit hash and release date, product and UI kind, remote name, whether this is a new installation, and anonymized machine, session, SQM and device identifiers. Those are generated and documented by VS Code itself and are not collected by this extension directly. VS Code does not inject anything describing the operating system, so this extension supplies the three properties below through createTelemetryLogger's additionalCommonProperties; they will be dropped again if VS Code starts injecting them.",
"common.os": {
"classification": "SystemMetaData",
"purpose": "FeatureInsight",
"comment": "The operating system family, as Node reports it: 'linux', 'darwin', 'win32', and so on. A fixed identifier from a short list, used to tell which platforms the features people use are actually used on."
},
"common.nodearch": {
"classification": "SystemMetaData",
"purpose": "FeatureInsight",
"comment": "The processor architecture, as Node reports it, for example 'x64' or 'arm64'. A fixed identifier from a short list."
},
"common.platformversion": {
"classification": "SystemMetaData",
"purpose": "FeatureInsight",
"comment": "The numeric part of the operating system version only, for example '7.2.2' or '10.0.22631'. Any build or distribution suffix is stripped before sending, because that suffix is the identifying part and is of no use for ranking features."
},
"notCollected": "This extension never sends file names, file paths, workspace or folder names, repository names, git remote URLs, branch names, tag names, commit hashes, commit messages, author names, email addresses, environment variables, credentials, or the list of other installed extensions. The receiving service stores no information which would be used to track deanonymize user."
}
}