Operations | Monitoring | ITSM | DevOps | Cloud

The latest News and Information on Monitoring for Websites, Applications, APIs, Infrastructure, and other technologies.

Slashing Development Costs in an Economic Downturn

Join leading practitioners from Apple, Wayfair, and Lightrun to discuss how to best confront the challenges that come with managing and operating an engineering organization in times of uncertainty, specifically in these troubling times of an ongoing recession. In this session, you will learn hands-on tips & tricks that will help you to.

Announcing Logz.io's Data Optimization Hub

To help our customers reduce their overall observability costs, we’re excited to announce the Data Optimization Hub as part of our Open 360™ platform. The new hub inventories all of your incoming telemetry data, while providing simple filters to remove any data you don’t need. Gone are the days of paying for observability data you never use.

Icinga DB Web search bar overview

With Icinga DB Web you can filter the list views in a very elegant and lovely manner. If you haven’t tried this search bar yet, it’s time to begin now. Unlike in the monitoring module, where you have to tediously filter the views based on clicking through all the possible selections available to you, in Icinga DB Web it’s a very simple thing where you can do it instantly.

NiCE VMware Management Pack 5.6 for Microsoft SCOM

Unlock business benefits by monitoring your VMware’s High Availability infrastructure. More performance, more availability, and more transparency. Get the most important advantages that extended VMware monitoring can offer with the new NiCE VMware Management Pack for Microsoft SCOM. Secure, protect, and manage large VMware environments and digital workspaces based on advanced analytics.

Sponsored Post

Outages ITOps professionals are thankful to avoid

As we settle into the time of year when we reflect on what we're thankful for, we tend to focus on important basics such as health, family and friends. But on a professional level, IT operations (ITOps) practitioners are thankful to avoid disastrous outages that can cause confusion, frustration, lost revenue and damaged reputations. The very last thing ITOps, network operations center (NOC) or site reliability engineering (SRE) teams want while eating their turkey and enjoying time with family is to get paged about an outage. These can be extremely costly - $12,913 per minute, in fact, and up to $1.5 million per hour for larger organizations.

Exoprise Survey Finds 90% of Remote Workers Face Productivity Challenges Due to Ongoing IT issues

In a post-COVID world, the best performing enterprises need to take an innovative approach to guarantee IT service reliability and optimize home networking stack for troubleshooting visibility.

How to Optimize the DevOps Pipeline Through Developer Workflows

The DevOps pipeline is a crucial part of software development, but it can often get mired in bottlenecks. Most problems are caused by the development and operations teams having different responsibilities are due to inefficiencies in the pipeline design. However, thanks to continuous observability, DevOps now gets a new lease of life since it is possible to tweak the pipeline to suit the developer’s workflow.

Observability and Its Influence on Scrum Metrics

Scrum metrics are an essential indicator of your team’s progress. In an agile team, they help you understand the pace and progress of every sprint, ascertain whether you’re on track for timely delivery or not, and more. Although scrum metrics are essential, they are only one facet of the delivery process — sure, they ensure you’re on track, but how do you ensure that there are no roadblocks during development? That’s precisely where observability helps.

Suspect Commits via Git Blame

Errors are part of building software. Even if you are one of the fabled 10X engineers, errors are still going to happen. When an error does occur, typically you are going to look at the stack trace to understand the why and who for triaging. But figuring out who to assign an issue to just based on the stack trace can be difficult. How many times do you see a stack trace in a Sentry issue, head to GitHub, and try to figure out who changed the line of code in question? Often would be our guess.