Operations | Monitoring | ITSM | DevOps | Cloud

Node.js monitoring is a tricky task. There are certain challenges to look out for. Because Node.js is a dynamically typed programming language and single-threaded you give the interpreter and runtime a lot of freedom to make decisions. This can easily result in memory leaks and high CPU loads. Parallel execution is simulated in Node.js by using asynchronous execution of functions. But, if a single function blocks the thread or event queue, the application performance will take a huge hit.

We all want better results with less effort. Automation increases reliability and improves quality. These truths mean that every software company out there is trying to accomplish a similar end result for their customers. But let's face it - no single company is going to get there alone, it's too big a job for just one tool. Your best option is to use the best tools for their specific feature sets... but make sure they play well together, in order to get the results you want.

Last week I told Blerim that Icinga came to life on 6.5.2009 … really, 10 years already? A small group of Nagios community members stood up and wanted to create more than a monitoring core with an enhanced web interface. APIs, integrations, backends, scaling, metrics, … A lot of passion and love was received from the community and actually, the Nagios ecosystem became more active again.

For years, traditional infrastructure provisioning and management followed a specific operating model that depended on Network Operations Centers (NOCs) to process operational events. As enterprise companies started to undergo digital transformation, the cloud created a different operating model: One that was much more agile and, some would argue, more efficient—and would replace all other operating models to create IT homogeneity.

Over the last year or so, I experimented with different ways of getting customer feedback for Checkly. This post is about what worked for us and how I was totally wrong about chat widgets.

This post illustrates some practical examples of distributed context propagation. More detailed examples are presented in Chapter 10 of my book, Mastering Distributed Tracing.

As OpsRamp continues the steady drumbeat of how AIOps can transform IT operations management, the industry continues to validate our positioning with recognition, press, and more. Three recent analyst reports highlighted OpsRamp’s modern digital and IT operations management platform for dynamic performance insights and maximum visibility. The company’s inclusion in these reports validates the growing need for a unified digital operations command center.

Everyone understands the importance of branding for a site or online business. When you are running an online business, it is important to present the brand objective along with your products and services with the help of a proper brand logo. When you wish to draw the attention of the target audience, a high-quality, cohesive brand image can help you achieve the same.

Understanding the context of an IT incident can greatly reduce the MTTR and enhance the ability to determine the root cause. In an IT environment, ‘context’ is used to refer to the subset of information necessary to troubleshoot and diagnose an incident, or event. For some scenarios, the context may be the downstream dependencies after a high availability pair of firewalls goes offline, and in others, it may be the datastore in contention from multiple VMs.