In version v1.32 of Netdata, we announced a remarkable new update that we are extremely proud of; Netdata Cloud now runs on the most reliable and stable backend that we’ve ever built. The architectural changes allow us to deliver new features, such as parent-child relationships and improved alert handling.
SIGNL4 integrates with various backend systems like IT monitoring, service management, IoT systems, sensors, etc. to automatically alert users and teams about certain incidents. A list of selected tools along with integration descriptions is available in our integrations section. How can you integrate SIGNL4 with your own tools? In the following we list some options offering different levels of sophistication.
A question we are hearing often is related to manager escalations, a heavily utilized feature in SIGNL4. Users ask us if those managers can be scheduled. The short answer is ‘yes’, but you need to use a different feature in SIGNL4 and do a little re-configuration.
We have released an update for Enterprise Alert 9 (version 9.3) that revolutionizes our OPC connector and also includes some bug fixes. Read all the details in this article.
When downtime strikes any distributed software deployment or platform, it's all hands on deck until the lights are green and service is restored. This process, from the recognition of a problem to a deployed solution, has most commonly been defined as MTTR - mean time to resolution. In just the last few years, DevOps and site reliability (SRE) professionals have developed sophisticated new models for how they work and audit their successes. In 2022, MTTR is one of the most widely-used software performance success metrics.
Over 85% of global organizations will be running containerized applications in production by 2025 say Gartner, with 4 in 5 enterprises expected to move their workloads from on-premises infrastructure to the cloud. Migration to the cloud has IT admins and/or SREs managing an increasingly complex, hybrid IT environment, with an uphill battle of trying to monitor and troubleshoot their infrastructure components and services in real time.
We’re continuing on with our third piece about how to utilize and improve your Intelligent Alert Grouping (IAG)! In case you missed it, the first two blog posts describe the feature (here) and explain how it uses merging to group alerts (here). We alluded to today’s post at the end of last: today we’ll be discussing how to use alert titles to improve IAG matches.
With the ScienceLogic SL1 platform correlating and contextualizing data to generate actionable events that accurately reflect the issues that need attention, how do you make sure all your engineers and system admins are on the same page?
