Operations | Monitoring | ITSM | DevOps | Cloud

Businesses lose potential revenue, trust, and brand reputation every moment your website is down. Some of those things can never be earned back. Website outages sting whether you’re a blossoming startup or a seasoned enterprise. How often do they happen, and what’s the actual cost? That is exactly what we will explore together today!

As your applications grow, your teams may be faced with managing a complex, expanding mesh of potentially thousands of loosely connected APIs—each one a new point of failure that can be difficult to track and patch. API sprawl comes naturally in rapidly expanding, distributed applications, and the difficulty of maintaining centralized knowledge and toolsets for your APIs creates friction when teams need to leverage APIs they don’t own.

Today’s modern applications are made up of thousands of loosely connected private and publicly exposed APIs, each serving a specific function. This dynamic API landscape, in combination with the decentralized nature of microservice development, can be overwhelmingly challenging to manage—let alone govern or secure adequately. API sprawl is often created as a result, leading to fragmented or nonexistent internal API documentation, knowledge bases, and toolsets.

Prometheus can be configured to read from and write to remote storage, in addition to its local time series database. This is intended to support long-term storage of monitoring data.

Collecting metrics about your servers, applications, and traffic is a critical part of an application development project. There are many things that can go wrong in production systems, and collecting and organizing data can help you pinpoint bottlenecks and problems in your infrastructure. In this article, we will discuss Graphite and StatsD, and how they can help form the basis of monitoring infrastructure.