One of the things we love about working in the cloud is the ease and scalability it brings to application development. It enables us to build out applications, APIs and any infrastructure that is needed from prototyping an idea, through to self scaling deployments. Monitoring and troubleshooting production-level serverless applications is always tricky, Especially working across a number of services and the many logs they can produce.

When developing the new exception landing pages we recently launched (like insert exception link here), I wanted to pull some statistics from Reddit. While looking through various ways to integrate, I found an easy approach that I want to share with you in this post. You probably already know Reddit, the highly active social news aggregation and discussion forum. I've found myself using Reddit more and more over the last couple of years, with the dotnet subreddit in particular.

Nate Lee here, and I’m one of the founders of Speedscale. The founding team’s worked at several observability and testing companies like New Relic, Observe Inc, and iTKO over the last decade. Speedscale traffic replay was borne out of a frustration from reacting to problems (even if they were minor) that could have been prevented with better testing.

ICYMI: in Part 1 of this blog post, I introduced Sensu Catalog Integrations, one of the three components that make the Sensu marketplace work. In this post, I want to cover the second piece, the Catalog API generator. This is the tool that consumes the github.com/sensu/catalog repository content and renders static http API content the Sensu web app can consume.