Those of you, who’ve already tried out the Web Interface for Icinga DB might have noticed the redesigned layout of the check execution statistics section in a monitoring object’s detail view. For all the others: Learn about it in this post. On first hand we wanted to make the informations more compact and put them in relation with each other, where possible. We aimed to keep all the information of the old one, though.
When you build your application on top of Lambda, AWS automatically scales the number of “workers” (think containers) running your code based on traffic. And by default, your functions are deployed to three Availability Zones (AZs). This gives you a lot of scalability and redundancy out of the box. When it comes to API functions, every user request is processed by a separate worker. So the API-level concurrency is now handled by the platform.
At Honeycomb, we talk a lot about eating our own dogfood. Since we use Honeycomb to observe Honeycomb, we have many opportunities to try out UX changes ourselves before rolling them out to all of our users. UX doesn’t stop at the UI though! Developer experience matters too, especially when getting started with observability. We often get questions about the difference between using our Beeline SDKs compared with other integrations, especially OpenTelemetry (abbreviated “OTel”).
What’s the buzz around AIOps? According to Gartner, “AIOps is the application of machine learning (ML) and data science to IT operations problems.” Though the terms AI and ML conjure images of almost magical capabilities, devoid of connection to the domain in which it’s applied, actually the reality is far different.
Since the release of Sensu Go, many in our community have told us Sensu is easier and faster to deploy, more portable, and more compatible with containerized and ephemeral environments (as compared to Sensu Core, the original version of Sensu). In a recent webinar, I talked about integrating Sensu Go with your CI/CD pipeline and how to use the sensuctl prune command to keep your Sensu resources in a declarative state, reducing dependence on traditional configuration management tools.
Since the release of Sensu Go, many in our community have told us Sensu is easier and faster to deploy, more portable, and more compatible with containerized and ephemeral environments (as compared to Sensu Core, the original version of Sensu). In a recent webinar, I talked about integrating Sensu Go with your CI/CD pipeline and how to use the sensuctl prune command to keep your Sensu resources in a declarative state, reducing dependence on traditional configuration management tools.
ServiceNow announced a new integration with Cisco DNA Spaces, a location-based application and analytics tool, to enhance COVID-19 contact tracing. The integration will use the Wi-Fi-enabled proximity reporting application to help organizations manage the return of employees to the workplace, as well as closely monitor workspaces, to maintain proper physical distancing. We’ve also added new capabilities to the ServiceNow Safe Workplace suite to make business travel safer and more manageable.
We’ve added a new feature to your monitoring settings, Concurrent Monitoring. Now you can choose to have Uptrends test from multiple locations at the exact same time. Not only will you have more data for your analysis, but you also get your alerts quicker leading to faster problem resolution.
In this article, I’ll try to guide you through some examples and definitions that aim to clarify the Web Vitals landscape from a Next.js perspective. Let’s dive in!
