-
Notifications
You must be signed in to change notification settings - Fork 218
Metrics#timeControllerExecution should include resource identifier #1324
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
Milestone
Comments
metacosm
added a commit
that referenced
this issue
Jul 11, 2022
metacosm
added a commit
that referenced
this issue
Jul 11, 2022
csviri
pushed a commit
that referenced
this issue
Jul 13, 2022
metacosm
added a commit
that referenced
this issue
Jul 13, 2022
Right now, the only metadata that's provided is the group/version/kind information associated with the resource being processed. Fixes #1322. Fixes #1324. Co-authored-by: csviri <[email protected]>
csviri
added a commit
that referenced
this issue
Jul 13, 2022
Right now, the only metadata that's provided is the group/version/kind information associated with the resource being processed. Fixes #1322. Fixes #1324. Co-authored-by: csviri <[email protected]>
csviri
added a commit
that referenced
this issue
Jul 13, 2022
Right now, the only metadata that's provided is the group/version/kind information associated with the resource being processed. Fixes #1322. Fixes #1324. Co-authored-by: csviri <[email protected]>
csviri
added a commit
that referenced
this issue
Jul 14, 2022
Right now, the only metadata that's provided is the group/version/kind information associated with the resource being processed. Fixes #1322. Fixes #1324. Co-authored-by: csviri <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I feel that it would make sense to add the ResourceId to either the
ControllerExecution
interface or the timeControllerExecution method as parameter.This way we could associate time measurements with reasources/namespaces etc. Currently the best we can do is to associate them to a resource type via the controller name.
The text was updated successfully, but these errors were encountered: