Operations | Monitoring | ITSM | DevOps | Cloud

This release provides fixes for the InfluxDB and Elasticsearch metric writers. If you’re using TLS connections, the latter were not closed correctly. In addition to these fixes, we’ve also backported fixes for delayed and one-time notifications. Special thanks to mdetrano for being patient and testing this one.

Hey brother, can you spare $5 million? That’s about what Amazon estimates it lost in sales back in 2013, when its website went down for around 40 minutes. For the math junkies out there, that’s $125,000 a minute, or $2,083.33 a second.

To fully understand what NetFlow is and why it’s used for network monitoring, we first need to know what a flow is. When computers need to talk to one another they establish communication channels, commonly referred to as connections. (Technically speaking, these communication channels can only be called connections when the TCP protocol is involved.) A flow refers to any connection or connection-like communication channel.

We’ve talked to a lot of people about their company’s digital employee experience the past few years – from C-suite executives and board members looking to make sure they’re doing what they can to make work lives better and retain staff, to the actual CIOs and IT managers tasked with changing and improving their employees’ workplace experience. We’ve even heard from employees on the front lines every day about what works and what doesn’t at their companies.

Organizations that depend on distributed systems often write their applications in Go to take advantage of concurrency features like channels and goroutines (e.g., Heroku, Basecamp, Cockroach Labs, and Datadog). If you are responsible for building or supporting Go applications, a well-considered logging strategy can help you understand user behavior, localize errors, and monitor the performance of your applications.

If you could know information about your systems in advance, what would you choose to know? If there was a set of repeating behaviors that happened consistently before an outage, would you want to know what they were? This is the idea behind proactive monitoring – the switching of context from “reactive” monitoring to something that allows you to act before the problem arises. Here are some guidelines to help you get started with your customized solution.

Most Citrix professionals are well aware that when desktop or application performance is slow, the first finger tends to get pointed at the Citrix team. But even for complex ecosystems like Citrix, ITIL guidance like a Service Desk continues to be a long-standing ‘best practice’ and can help if IT staff work together. This post will outline some of the ITIL guidance from the perspective of eG Enterprise and a Citrix-based digital workspace.