When it comes to complex application integrations, RED monitoring provides a sensible and necessary common element to see how our systems are performing and to alert us to behavior which is detrimental to your customers and your business goals. So, what is RED? RED stands for rate, errors, duration and is an offshoot of the Google Golden Signals.

With more and more endpoints accessing your network remotely, you should expect rapid increases in VPN connections and usage, as well as exponential usage of cloud-based services. There are numerous Splunk apps that can help you increase the monitoring of remote endpoints but let’s showcase Splunk Security Essentials (SSE).

Our SAP ambassador Brian Paul offers his insights on the value that Cisco and AppDynamics bring to SAP customers.

Unit tests and integration tests are vitally important, but sometimes even those aren’t sufficient to ensure that critical services in your application will function smoothly in production. In those cases, adding a staging step to our CI/CD process allows us to test a feature with real data in a less supervised environment. For example, here at Lumigo we decided to use it for our Node.js tracer.

Telemetry is the collection of measurements or other data at remote or inaccessible points and their automatic transmission to receiving equipment for monitoring. In network telemetry, network devices such as routers, firewalls and switches push real-time data continuously to one or more centralized locations for storage, processing and analysis.

In the previous blog post Data analytics with Jaeger aka traces tell us more! we have introduced our data science initiative and platform. The ultimate goal is to develop new functionality within the Jaeger project based on AI/ML that will provide new insights into our applications. This type of functionality is also referred to as AI operations (AIOps). Jupyter notebooks provide a simple user interface for experimenting with data.

Your phone is ringing off the hook. Another client is calling, trying to figure out how to ensure their team can continue to be productive in the wake of the COVID-19 pandemic. Even though these are extraordinary times, your role as the IT professional hasn’t really changed. Your job is to make sure your clients are productive and they can still access the resources, tools, and applications they need to do their jobs.

Has your phone gone in the middle of the night when your boss is calling because the server is down? Maybe you wake up to a tone of text messages that something is wrong with the server? If you have encountered this, then you know the importance of monitoring your server so that you are not the last to know when there is a problem. Part of server monitoring is putting best practices in place to ensure you are prepared for the unexpected.

Over the last 10 years, the landscape that we manage, maintain, and control as operators and developers has changed dramatically. We’ve shifted from monolith to microservices, from bare metal to VMs to containers to function-based computing — and it’s changed how we need to approach monitoring and observability.

The end of TLS v1.0 and v1.1 is near – the most popular browsers will either display a warning message when you visit a TLS 1.0/1.1 site or require user intervention and confirmation to connect to the website.