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.

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

v1.5: Activate /metrics via /experimental-features route #2593

Closed
2 of 3 tasks
guimachiavelli opened this issue Oct 25, 2023 · 1 comment · Fixed by #2612
Closed
2 of 3 tasks

v1.5: Activate /metrics via /experimental-features route #2593

guimachiavelli opened this issue Oct 25, 2023 · 1 comment · Fixed by #2612
Labels
new release Changes related upcoming Meilisearch releases
Milestone

Comments

@guimachiavelli
Copy link
Member

guimachiavelli commented Oct 25, 2023

/metrics is an experimental feature allowing users to obtain more data on their instance. It can be activated with a command-line flag.

With v1.5, users will also be able to activate it with the /experimental-features API route:

curl \
  -X PATCH 'http://localhost:7700/experimental-features/' \
  -H 'Content-Type: application/json'  \
  --data-binary '{
    "metrics": true
  }'

Tasks

  • Update /learn/experimental/metrics.mdx
  • Update table in /learn/experimental/overview.mdx
  • Update API reference (object, responses)

References

@guimachiavelli guimachiavelli added this to the v1.5 milestone Oct 25, 2023
@curquiza
Copy link
Member

@guimachiavelli if I'm correct you don't have to change anything on https://www.meilisearch.com/docs/learn/experimental/metrics since the behavior is not described

@curquiza curquiza added the new release Changes related upcoming Meilisearch releases label Oct 31, 2023
@guimachiavelli guimachiavelli linked a pull request Nov 16, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new release Changes related upcoming Meilisearch releases
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants