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
Problem Statement
History make it possible to reactively check who made a change to an object, but there is no way to proactively check changes. For example, someone make a change by mistakes, admin will need to wait to receive complaints from customers to identifies why and who made the mistake.
Describe the solution you'd like
A way to proactively monitor changes is to log all the changes to STDOUT. Using some others tools (log collectors, monitoring tool etc.), it's then possible to use these logging to integrate to some messaging apps (slack etc.).
Describe alternatives you've considered
Probably no other easy win.
Additional context
None.
The text was updated successfully, but these errors were encountered:
Problem Statement
History make it possible to reactively check who made a change to an object, but there is no way to proactively check changes. For example, someone make a change by mistakes, admin will need to wait to receive complaints from customers to identifies why and who made the mistake.
Describe the solution you'd like
A way to proactively monitor changes is to log all the changes to STDOUT. Using some others tools (log collectors, monitoring tool etc.), it's then possible to use these logging to integrate to some messaging apps (slack etc.).
Describe alternatives you've considered
Probably no other easy win.
Additional context
None.
The text was updated successfully, but these errors were encountered: