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
Is your feature request related to a problem? Please describe.
As a user that is bound by security policies (SOC, ISO27001, etc). Any change to production needs to be approved and reviewed. It should be possible to have this ability with DEEP tracepoints.
As a tracepoint can collect any data, and expose it to others. It should be subject to the same rules as any MR/PR. It should therefore be possible to allow a tracepoint to be created, then put into review. Where another user would need to approve it before it is activated by the service.
In a similar vain this would also require audit logs of the tracepoints being created/modified and approved. See ...
Describe the solution you'd like
Once a tracepoint is created it is stored as 'pending' then a review can be performed to ensure these tracepoints are ok. Once approved the tracepoint can be activated and sent to the clients.
It could also be possible to preapprove certain tracepoints, if they are deemed safe.
Describe alternatives you've considered
Possible integration into Github/GitLab to provide a repo that contains the configs. This would allow the existing MR/PR approaches to be used.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
As a user that is bound by security policies (SOC, ISO27001, etc). Any change to production needs to be approved and reviewed. It should be possible to have this ability with DEEP tracepoints.
As a tracepoint can collect any data, and expose it to others. It should be subject to the same rules as any MR/PR. It should therefore be possible to allow a tracepoint to be created, then put into review. Where another user would need to approve it before it is activated by the service.
In a similar vain this would also require audit logs of the tracepoints being created/modified and approved. See ...
Describe the solution you'd like
Once a tracepoint is created it is stored as 'pending' then a review can be performed to ensure these tracepoints are ok. Once approved the tracepoint can be activated and sent to the clients.
It could also be possible to preapprove certain tracepoints, if they are deemed safe.
Describe alternatives you've considered
Possible integration into Github/GitLab to provide a repo that contains the configs. This would allow the existing MR/PR approaches to be used.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: