Healthchecks recently gained a new feature: check auto-provisioning. When you send a ping request to a slug URL, and a check with the specified slug does not exist, Healthchecks can now automatically create the missing check. This feature requires opt-in: to use it, add a?create=1 query parameter to the ping URL.
When we make a request to your site to verify that your site is up, the response of your server will contain certain headers. We can verify that those headers contain the values you expect. If these expectations are not met, we'll consider your site as down. In the "Responses" section of the uptime settings page, you can specify which headers we should verify. You could add this expectation to ensure your page uses gzip compression.
What is the difference between logs and events in observability? These two telemetry data types are used for different purposes when it comes to exploring your applications and how your users interact with them. Simply put, logs can be used for troubleshooting and root cause analysis, while events can be used to gain deeper application insights via product analytics. Let's review some application telemetry data definitions for context, then dive into the key differences between logs and events and their use cases. Knowing more about these telemetry data types can help you more effectively use them in your observability strategy.
The observability landscape is constantly changing and evolving. Despite this, one question often plagues operations leaders: "How can we consolidate disparate data sources and tools to view system performance comprehensively?" These leaders have sought the answer in a single-pane-of-glass solution. However, as Jason Bloomberg and Buddy Brewer discussed in the Mezmo webinar "Solving the Single Pane of Glass Myth," this idea is more myth than reality.
Take back control of your Monitoring with Levitate - a managed time series data warehouse.
