Operations | Monitoring | ITSM | DevOps | Cloud

Microservices interact in so many ways. Load balancers, security authentication, and service discovery are just the tip of the iceberg. It can get confusing, if not outright messy. But why be messy when you can be meshy? This is where service meshes come into play, linking the roles these tools have in a common ‘net’ that ties and weaves the whole architecture together. Hashicorp has produced one of the most popular of these organizational assets — Consul Connect.

As more and more organisations dive into Azure, storage consumption continues to grow and so does the cost to businesses. Azure offers almost a limitless supply of storage, but this comes at a cost so it’s important to know exactly where that storage is going. There are a few ways to get this information, either via the Azure portal, Azure Storage Explorer or even PowerShell. However, all these tools have limitations and to be honest, rather lacking and not that straightforward.

Since the launch of ITIL 4, incorporating DevOps into service management strategy has been a hot topic. On the surface, both DevOps and ITIL are frameworks that can help facilitate successful operations surrounding IT services. But that doesn’t mean that IT pros need to choose one or the other. Like most great marriages, it’s how these two methodologies complement each other that makes them an ideal pair when it comes to ITSM.

Robert Greiseimer has called Go the language of cloud computing and while it’s no secret that Go has strong features that support the needs of microservice architecture, distributed systems, and large-scale enterprise applications, what is less talked about is that Go was also built with web development in mind from the start. In fact, many developers in the community are using Go for full-stack development and championing new modules and frameworks that make Go a strong language for the web.

The DevOps India Summit brings together some of the best thought leaders in the DevOps space to discuss and debate everything DevOps related. This year, the event was a virtual one, held in a virtual venue with a virtual lobby, exhibit hall, booths, and a virtual auditorium for speakers presenting online.

Health and performance issues are easier to understand—and to troubleshoot—when you can use tags to aggregate your data across many overlapping scopes. But while some scopes come directly from your infrastructure, others are constantly evolving to reflect the needs of your product or organization. You can only track your data effectively if you can define—and redefine—your scopes on the fly.

The v1.25.0 release of the Netdata Agent delivers on our commitment to make our metrics collection, visualization, and troubleshooting platform more stable and usable. We enhanced our recently-added Prometheus collector with user-configurable filtering and grouping, made dramatic improvements to the reliability of the Agent-Cloud link that streams metrics on-demand to your browser when you use Netdata Cloud, and more. Let’s jump in and look at each improvement.

When an incident strikes, and every minute spent on root cause analysis delays the time to resolution, the real-world consequences can be dire. Troubleshooting an event requires a certain data set: every metric, at the greatest granularity, in one place, available in real time. Limits on the number or type of metrics, collection frequency, or time to visualization can mean the difference between timely resolution and unacceptable losses in time, money, and productivity.