Operations | Monitoring | ITSM | DevOps | Cloud

Blog

Comparing a Multi-Tenant SaaS Solution vs. Single Tenant

Let me preface this article with a quick customer story. I was recently talking with the director of operations of a G2000 company and he asked in a nice, but pointed way: “All I want is a SaaS software solution to manage my applications. Why does the architecture of the software matter?”. At Sumo Logic, we couldn’t agree and disagree more.

Jaeger vs Zipkin - OpenTracing Distributed Tracers

In the previous three parts of our OpenTracing series, we provided an Overview of OpenTracing, explaining what OpenTracing is and does, how it works and what it aims to achieve, we looked at Zipkin – a popular open-source distributed tracer and then at Jaeger – a newer open-source distributed tracer developed under the CNCF umbrella. In this blog post – the last part of the OpenTracing series – we will compare Jaeger vs. Zipkin side by side!

Build and Run a Honeycomb Query right from your URL bar with Query Template Links

Whenever you run a Honeycomb query, you’re directed to the permalink for the results. Returning to this URL always supplies the same data without re-running the query, which is important when sharing links to make sure that everybody is looking at the same thing. However, there may be cases where you want a link not to a specific set of results, but to a set of query parameters which are re-run automatically. Further, you may want to generate these links without relying on the Honeycomb UI.

The power of proposals (and open source culture)

I come from a world where strategy is best kept secret. Whether it be from a company who has a codename for literally everything, or the competitive culture of playing and coaching D1 athletics, confidentiality became a required skill. Meetings, trainings, code reviews, scouting reports… anything of significance happened behind closed doors. In other words, definitely not open source.

Introducing Sentry 9

Errors. We all cause them all the time, which can make it difficult to figure out the person or team who should be responsible for fixing individual issues. Time that could be spent resolving an issue is instead spent tracking down who should be handling it and what it’s even about. This is a waste. It balloons time to resolution, often from minutes to hours or sometimes even days.

Support for AWS Application Load Balancer in the Honeycomb AWS Bundle

When we announced support for ingesting AWS Elastic Load Balancer access logs to Honeycomb, one of the first follow-up requests was for us to add support for AWS Application Load Balancer as well (which, alongside the Network Load Balancer, represents ELBv2). Given the list of features that ALB supports, it’s not difficult to see why. Who doesn’t want microservice-friendly path routing, native HTTP/2 support, tight integration with Amazon’s container-related services, and more?