-
Notifications
You must be signed in to change notification settings - Fork 58
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
Telemetry and logging #551
Comments
Hello @Alirexaa |
Is this feature still experimental? Also we need tracing too. |
What the point of having telemetry on the client side? Or do you mean being able to activated the experimental feature on the client side?
Are the meilisearch logs not enough? https://www.meilisearch.com/docs/learn/configuration/instance_options#log-level |
I'll explain to you in more detail. Metrics:You point out that meilisearch exposes some metrics but I don't see any API in the client to get these metrics, so I mean active this feature on the client side. Also, add some ability for the client to get these metrics in some regular period (for example get metrics every 5 seconds to show metrics on charts) this ability should be for easy integration of the meilisearch-dotnet client to user applications. Tracing:Just like other dotnet applications that use Define activity resource: The client should support tracing for every request sent to meilisearch. Logginglogging should support in client side. These logs are not related to meilisearch, it's related to the client side. |
Description
Could this Client support OpenTelemetry (including tracing, metrics, and logs)?
The following link helps with how to implement it.
https://opentelemetry.io/docs/languages/net/instrumentation/
The text was updated successfully, but these errors were encountered: