-
Notifications
You must be signed in to change notification settings - Fork 219
Metrics improvements #1472
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
Comments
All of this sounds reasonable. 😄 |
There's an HTTP client independent interceptor interface in Fabric8 6: https://github.com/fabric8io/kubernetes-client/blob/master/kubernetes-client-api/src/main/java/io/fabric8/kubernetes/client/http/Interceptor.java |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
Just some thoughts: It would be possible to do a metric to measure resource event received and first processed time delay. But event this might be an issue if there is already a reconciliation running - that might also complicate things. So queue since and thread count might be a simpler indicator to measure the pressure on the operator I guess. |
will close this issue, added then mentioned metrics, expect the one I commented above, and informer count (since it might not trivial to add in the current architecture, also it's fairly simple, in general if the namespaces are not changing dynamically are static values). In case @morhidi you think it still makes sense pls create a separate issue for that. |
Thanks @csviri |
Uh oh!
There was an error while loading. Please reload this page.
Hi team,
we've successfully implemented and using the existing
Metrics
interface from JOSDK in the Flink Operator. Great job!We'd be happy to see a few more metrics and improvements around the following areas:
Metrics
interfaceLet me know what you think.
Thanks,
Matyas
The text was updated successfully, but these errors were encountered: