Submitted via IRC for SoyCow1984
As companies shift to CI/CD (continuous integration/continuous delivery), they face a problem around monitoring and fixing problems in builds that have been deployed. How do you deal with an issue after moving onto the next delivery milestone? Harness, the startup launched last year by AppDynamics founder Jyoti Bansal, wants to fix that with a new tool called 24×7 Service Guard.
The new tool is designed to help companies working with a continuous delivery process by monitoring all of the builds, regardless of when they were launched. What's more, the company claims that using AI and machine learning, it can dial back a problematic build to one that worked in an automated fashion, freeing developers and operations to keep working without worry.
[...] The tool watches every build, even days after deployment, taking advantage of data from tools like AppDynamics, New Relic, Elastic and Splunk, then using AI and machine learning to identify problems and bring them back to a working state without human intervention. What's more, your team can get a unified view of performance and the quality of every build across all of your monitoring and logging tools.
So what do you think? Are you using Continuous Delivery in your shop and if so, how is that working out for you?
(Score: 2, Insightful) by bmimatt on Friday December 21 2018, @12:40AM
There are, you know, things like versioning, tagging, artifact repositories (also versioned, tagged).
We've been auto-rolling back deployments with simple shell scripts and the like for quite a while now.
Some of them wired up to monitoring, so they can be triggered automatically, too.
TFA is keyword-pimping hype. You don't need "AI" (read: ML) for this shit.