Operations | Monitoring | ITSM | DevOps | Cloud

StackState has always believed in the importance of open source and open standards, and we’ve demonstrated our commitment through ongoing support of open technologies. From the beginning, StackState supported StatsD and OpenMetrics. Even our agent is open source, designed to help organizations easily onboard our platform and to give them an extensible open way to observe their services. StackState is now proud to announce our next big open source step.

Enterprise data systems are like busy family households. You see a constant flow of activity to varying degrees from room to room. This activity includes people wandering, opening and closing doors. And then there are other streams constantly flowing through the household- electricity, water, Wi-Fi networks and more. In modern enterprises, the data deluge is a critical issue. While we take the complexity for granted in a household, such is not allowed in a connected enterprise.

TechStrong CTO and cofounder Mitch Ashley sat down with Lodewijk Bogaards, Brian Dawson and Cyrille Le Clerc, three industry experts to discuss the present and future of observability. Want to hear everything these experts have to say about the future of about the future of observability?

Microservices architecture allows technology companies to build application services around business capabilities. It enables rapid development and also boosts developer productivity. But it also introduces complexity. Troubleshooting and operating an internet-scale application based on microservices is hard. And that’s where distributed tracing comes into the picture. Traditional monolithic application architecture is easy to develop, deploy and monitor.

To supervise the behavior of distributed applications and track the origin of service failures and downtime, developers often use traditional monitoring technologies and tools. However, this approach can fall short in its ability to measure the overall health of modern cloud-native architectures, which can span multiple hosting environments and encompass hundreds of microservices.

SRE (site reliability engineering) is a discipline used by software engineering and IT teams to proactively build and maintain more reliable services. SRE is a functional way to apply software development solutions to IT operations problems. From IT monitoring to software delivery to incident response – site reliability engineers are focused on building and monitoring anything in production that improves service resiliency without harming development speed.