I really like the idea of AI DevOps. Instead of dashboards and reactive observability, we are all in the presence of a general purpose system that takes action, logs those actions in explainable form, and can easily control a production system.
The detail work from the engineer here where he suppresses the "purposefully" caused 429 errors and amplifies the errors coming from other non-noisy tenants during the usage spike is pretty powerful too.
I am quite proud of the team and of this solution--especially considering it isn't coming from MyDecisive engineers but from an end user. Please help us bring more ideas like this to light. This HN community is smart and powerful and we welcome everyone's ideas and contributions.
I really like the idea of AI DevOps. Instead of dashboards and reactive observability, we are all in the presence of a general purpose system that takes action, logs those actions in explainable form, and can easily control a production system.
The detail work from the engineer here where he suppresses the "purposefully" caused 429 errors and amplifies the errors coming from other non-noisy tenants during the usage spike is pretty powerful too.
I am quite proud of the team and of this solution--especially considering it isn't coming from MyDecisive engineers but from an end user. Please help us bring more ideas like this to light. This HN community is smart and powerful and we welcome everyone's ideas and contributions.
Thanks for your time!