Incident management is easily one of the most annoying things anyone has to ever deal with. There will always be only a handful of people who would ever want to walk into the building on fire to mitigate. That’s the same with most engineering teams. Only a handful are willing to get in, find the root cause, and mitigate the incident.
Heroku is a cloud provider well known for its simplicity and its support out of the box for multiple programming languages. When thinking about consuming logs from applications hosted in Heroku, Grafana Loki is a great choice. But in the past, shipping logs from Heroku to any Loki instance required ad-hoc scripts to fiddle with Heroku’s logs format and send them. This can be a time-consuming experience.
If you’ve ever had a website or service go down as you were using it, then you’ll understand the irritation of a generic error message and a plea to “Be patient!” (if you’re lucky). It’s almost like they know they’re not telling you the full story. The companies that are on top of their outage game will have a prepared link or redirect to their Status Page (or at least, have one prominently displayed on their pages and social media) for times like these.
Mergers and acquisitions are complex. So complex, in fact, that up to 90% fail. One of the biggest risks for M&A failure comes during technology integration. At this stage, enterprise security, compliance, and employee productivity can all be irreparably disrupted. IT needs to walk a fine line between staying on schedule and maintaining stability.
We are excited to announce the new CircleCI Config SDK is now available as an open-source TypeScript library. Developers can now write and manage their CircleCI config.yml files using TypeScript and JavaScript. For developers used to the ecosystem and flexibility of a full-fledged programming language, sometimes YAML can feel limiting or intimidating. With the Config SDK you can define and generate your YAML config from type-safe and annotated JavaScript.
With distributed IT Operations becoming the norm, most enterprise teams struggle with communication and collaboration within and across the organization. Without the proper tools, staying on top of incidents can be challenging, quickly resulting in outages taking longer to resolve. The overall effect: increase in downtime-related costs and decrease in performance and availability of services making mean time to resolve (MTTR) worse.
