We use energy in many different ways in our lives, be it for lighting up our houses, running electronic appliances or as fuel in our vehicles. There are mainly two types of energy: renewable energy and non-renewable energy. Non-renewable energy includes fossil fuels like natural gas, petroleum and coal. However, these energy sources come from nature itself; it is impossible to renew them quickly. This means that these resources will become entirely exhausted in the upcoming years.

A Webhook is an API that delivers data from applications when an action or event occurs. When an event is triggered within the source site, it is seen by the Webhook, which collects the data and sends it to the desired application or URL in the form of an HTTP request. Webhooks are also instant, triggering the delivery of data in real-time, this makes them faster and easier to implement than other methods, like polling.

When running and maintaining an application in a production environment, we want to feel confident about the behavior of the application and know when it isn’t working as expected. At the least, we want to track errors, monitor performance, and collect specific metrics throughout the application.

Say you've been tasked with monitoring an application, so you set up some alerts to let you know when errors are coming in. The minutes roll by, the errors start coming... ...and they don't stop coming... Oh my, there seems to be quite a few errors coming through. Alerting on each error isn't going to help, better report on changes in the error rate instead right? Not quite.

Have you always wanted to have different settings between production and staging but never knew how? You can do this with Kustomize! Kustomize is a CLI configuration manager for Kubernetes objects that leverage layering to preserve the base settings of the application. This is done by overlaying the declarative YAML artifacts to override default settings without actually making any changes to the original manifest.

After many weeks of work, we're delighted to announce the latest feature of the incident.io platform: Workflows. Configure your processes once, and we'll make sure you follow them, every time ✨ A little while ago, I was asked the question: “what makes a good incident response?”. Whilst there’s infinite nuance in the answer, mine was pretty straightforward. The best incidents are founded on principles of communication, coordination, and clear roles and responsibilities.