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.
Mangle doesn’t have running faults at random order feature at present. Mangle enables users to define fault schedules to run the faults at specified schedule. Schedule feature enables running of faults in a controlled manner and running of parallel faults on the same target at the same time.
Describe the solution you'd like
we could select ootb fault injections and/or the ones that we created ourselves and then we let them randomly be applied on the environment of our choice - not defined within a specific schedule but at unknown timings - log when what was injected so that we can afterwards do our RCA and check our observability and monitoring tools for lessons learned and adapt processes / workflows
Describe alternatives you've considered
none for the time being
Additional context
none for the time being
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Mangle doesn’t have running faults at random order feature at present. Mangle enables users to define fault schedules to run the faults at specified schedule. Schedule feature enables running of faults in a controlled manner and running of parallel faults on the same target at the same time.
Describe the solution you'd like
we could select ootb fault injections and/or the ones that we created ourselves and then we let them randomly be applied on the environment of our choice - not defined within a specific schedule but at unknown timings - log when what was injected so that we can afterwards do our RCA and check our observability and monitoring tools for lessons learned and adapt processes / workflows
Describe alternatives you've considered
none for the time being
Additional context
none for the time being
The text was updated successfully, but these errors were encountered: