Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add Telemetry #720

Closed
qdequele opened this issue May 27, 2020 · 0 comments · Fixed by #718
Closed

Add Telemetry #720

qdequele opened this issue May 27, 2020 · 0 comments · Fixed by #718
Assignees
@qdequele

Comments

@qdequele
Copy link
Member

qdequele commented May 27, 2020 •
edited
Loading

It's helpful for MeiliSearch's engineers and decision-makers to be able to measure how MeiliSearch behaves in the real world. The Telemetry feature provides this capability by sending performance and usage info to MeiliSearch Team. As you use MeiliSearch, Telemetry measures and collects non-personal information, such as performance, usage, and customizations.

Every machine has an UserId, this UserId guarantee the user privacy and is created by hashing username + hostname + platform.

We already have a ping each day. This helps us to measure the number of launch and the number of servers active since x days.

It's possible to deactivate all these analytics by adding on your environment MEILI_NO_ANALYTICS=true.

We would like to add:

  • The application version: Segment version
  • The environment: Segment development/production.
  • The number of days since the first start: Segment development/production.
  • The user email: (*Optional) If the user wants to have alerts
  • The server provider: (*Optional) To help us to know on which platform we have the biggest community.
  • The database size: Understand user usage
  • The last update: Segment development/production & understand user usage.
  • The number of updates per index: Understand user usage.
  • The number of documents per index: Understand user usage.

*Optional: Mean it's your choice to add this information by adding the right environment variables. MEILI_USER_EMAIL= andMEILI_SERVER_PROVIDER=
@qdequele qdequele linked a pull request May 27, 2020 that will close this issue
Add more analytics #718
Merged
@qdequele qdequele self-assigned this May 27, 2020
@bidoubiwa bidoubiwa mentioned this issue Jun 2, 2020
Merged
19 tasks
@fharper fharper mentioned this issue Feb 16, 2021
Closed
bors bot added a commit that referenced this issue Jan 16, 2023
@bors @loiclec
Merge #720
46e26ab 
720: Make soft deletion optional in document addition and deletion + add lots of tests r=irevoire a=loiclec

# Pull Request

## What does this PR do?
When debugging recent issues, I created a few unit tests in the hopes reproducing the bugs I was looking for. In the end, I didn't find any, but I thought it would still be good to keep those tests. 

More importantly, I added a field to the `DeleteDocuments` and `IndexDocuments` builders, called `disable_soft_deletion`. If set to `true`, the indexing/deletion will never add documents to the `soft_deleted_documents_ids` and instead perform a real deletion of the documents from the databases.

For the new tests, I have:
- Improved the insta-snapshot format of the `external_documents_ids` structure
- Added more tests for the facet DB indexing, deletion, and search algorithms, making sure to test them when the facet DB contains strings (instead of numbers) as well.
- Added more tests for the incremental indexing of the prefix proximity databases. For example, to see if documents are replaced correctly and if common prefixes are deleted correctly.
- Added tests that mix soft deletion and hard deletion, including when processing batches of document updates. 


Co-authored-by: Loïc Lecrenier <loic.lecrenier@me.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@qdequele qdequele

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add more analytics meilisearch/meilisearch
1 participant
@qdequele