We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello!
I am using github.com/zitadel/zitadel-go/v3/pkg/client to manage Zitadel from my application and I'd like to monitor my outgoing requests.
While there is one way of doing so by writing a custom Zitadel client wrapper that collects metrics, I think it would be better and easier for end users to pass prometheus interceptor (https://github.com/grpc-ecosystem/go-grpc-middleware/tree/main/providers/prometheus) directly to grpc connection.
Would you consider adding new client.Option for this purpose?
The text was updated successfully, but these errors were encountered:
I think this could be a great addition 👍
WDYT @zitadel/engineers
Sorry, something went wrong.
I think this is a great idea. I would prefer to use otel instead of a proprietary product.
🎉 This issue has been resolved in version 2.3.0 🎉
The release is available on GitHub release
Your semantic-release bot 📦🚀
No branches or pull requests
Hello!
I am using github.com/zitadel/zitadel-go/v3/pkg/client to manage Zitadel from my application and I'd like to monitor my outgoing requests.
While there is one way of doing so by writing a custom Zitadel client wrapper that collects metrics, I think it would be better and easier for end users to pass prometheus interceptor (https://github.com/grpc-ecosystem/go-grpc-middleware/tree/main/providers/prometheus) directly to grpc connection.
Would you consider adding new client.Option for this purpose?
The text was updated successfully, but these errors were encountered: