Operations | Monitoring | ITSM | DevOps | Cloud

As companies start their Kubernetes and cloud-native journey, cloud infrastructures and services grow at a rapid pace. This happens all too often as organizations shift left without thorough controls, which can lead to overallocating and overspending on their Kubernetes environments. Organizations running workloads in the cloud can put budgets at risk when they lack information about key facts.

Today we continue on our journey towards being API-first with two new updates – non-expiring tokens and regenerating API keys. As you may have seen, late last month we made the exciting announcement about the launch of our Public API. Delivering a world-class API is a core focus here at Raygun. We’re on a mission to give you greater control over how you can extract, manipulate, and visualize the powerful insights surfaced in Raygun, so that you can use them in exciting new ways.

Having a healthy network is essential for any online business. Downtime can be costly; if you're not monitoring your devices, you could have more downtime than you realize. Routers, in particular, are essential for keeping a network running. Routers are critical equipment for any business that relies on the Internet to communicate with customers or clients. A slow or faulty router can grind business to a halt, which is why keeping an eye on your router's performance is essential.

A couple of weeks ago, I had the opportunity to attend AWS re:invent, one of the biggest cloud industry events of the year. An event so massive and big that only AWS can pull it off – 50,000 people marching across half a dozen of the finest hotels on the Las Vegas strip. The expo hall alone would have taken more than a couple of days to cover all the vendor booths spread across the expansive Venetian convention center.

Finding service relationships and diagnosing bottlenecks within an application can be incredibly difficult to accomplish, especially if your applications are spread across multiple services, with both internal and external service calls. Although users could get granular visibility into individual traces using our Distributed Tracing features, they couldn’t see how their services were connected across different traces.