You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if an /event api could be configured for overlaybd-tcmu to use when certain lifecycle events happen, similar to how tcmu will can be configured with an /auth api.
Why is this needed for Overlaybd?
From a sys-admin perspective it would be extremely useful to know when background downloading has completed and overlaybd-tcmu has swapped to the local version. Today that information is available but it needs to be parsed from overlaybd.log. This is not ideal as the log schema could change. Instead, if an /event api could be configured, then metadata could be propagated to monitoring tools. What would also be useful is if the same traceid set w/ /auth was included in the data written to this api.
Are you willing to submit PRs to contribute to this feature?
Yes, I am willing to implement it.
The text was updated successfully, but these errors were encountered:
What is the version of your Overlaybd
No response
What would you like to be added?
It would be nice if an
/event
api could be configured for overlaybd-tcmu to use when certain lifecycle events happen, similar to how tcmu will can be configured with an/auth
api.Why is this needed for Overlaybd?
From a sys-admin perspective it would be extremely useful to know when background downloading has completed and overlaybd-tcmu has swapped to the local version. Today that information is available but it needs to be parsed from
overlaybd.log
. This is not ideal as the log schema could change. Instead, if an/event
api could be configured, then metadata could be propagated to monitoring tools. What would also be useful is if the sametraceid
set w//auth
was included in the data written to this api.Are you willing to submit PRs to contribute to this feature?
The text was updated successfully, but these errors were encountered: