Operations | Monitoring | ITSM | DevOps | Cloud

Honeycomb

Use New Range Markers to Show The Duration of a State Change

In our world of distributed systems, state changes to your infrastructure often take some time to propagate. With a few exceptions (for example, feature flags), single point in time changes are rare. Deploys, outages, database migrations, failovers, stress tests; none of these things are instantaneous – all have some duration during which the system is changing.

Instrument Your Ruby App In Minutes with the Honeycomb Beeline for Ruby

Meet the Honeycomb Beeline for Ruby. Like our Beelines for Go and Node, it understands the common packages you’re using and automatically instruments them to send useful events to Honeycomb. Then once you’ve got a chance to explore your app’s behavior, you can add custom fields specific to your app with just one line of code.

Honeycomb goes Serverless: Send your app data without running agents

Serverless apps are growing in popularity, thanks to tools like AWS API Gateway and Lambda, and a growing number of powerful frameworks that simplify development and deployment. Complex applications are still complex, however, and regardless of your platform you’ll still need to think about observability.

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.

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?