Skip to content
This repository has been archived by the owner on Mar 21, 2024. It is now read-only.

Telemetry - Add x-meilisearch-client query parameter #145

Merged
merged 3 commits into from
May 16, 2022
Merged

Telemetry - Add x-meilisearch-client query parameter #145

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ec316d8
Introduce the x-meilisearch-client query parameter
gmourier Apr 26, 2022
83fbfb0
Update text/0034-telemetry-policies.md
gmourier Apr 26, 2022
81fd943
Update text/0034-telemetry-policies.md
gmourier Apr 26, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions text/0034-telemetry-policies.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -417,6 +417,12 @@ The `User-Agent` header is tracked on the events listed below. Our official SDKs

Each endpoint API tracked sends the `User-Agent` as a `user_agent` event property as an array. If several values are contained in the `User-Agent` header, they are split by the `;` character.

##### `x-meilisearch-client` Query Parameter

Some browser engines prevent overloading the User-Agent header. To track the calls made by some clients concerned by this fact, e.g. the JavaScript SDK, it is possible to use the `x-meilisearch-client` query parameter.

If the query parameter is encountered, it overrides the presence of the `User-Agent` header.

#### Identifying MeiliSearch installation

To identify instances, we generate a unique identifier at first launch if analytics are not disabled.
Expand Down