Operations | Monitoring | ITSM | DevOps | Cloud

An oft-forgotten component of robust, production-ready code is testing. The moat protects us from costly service interruptions and fortifies trust in our product with our customers. Simply put, it’s in the critical path of damn good software. However, as we scale a cloud product to serve a rapidly growing user base, our test case scenarios scale correspondingly. As far as testing goes, end-to-end (E2E) testing most closely mirrors the end-user experience.

While spring is traditionally the time for tidying up for most folks, IT and Security teams know it is important always to maintain a clean, streamlined environment. However, we understand that doesn’t always happen with growing data volumes, stagnant budgets, and changing organizational priorities. This blog is to help you understand if you are properly overdue for a clean-up.

System monitoring can be viewed as being closely related to infrastructure monitoring, but there are differences between the two concepts, particularly with their scopes within the realm of IT monitoring. Infrastructure monitoring concentrates on monitoring the physical and virtual components of an IT environment, such as servers, networks, storage systems, and cloud services.

We present five common myths about platform engineering — what it is and what it isn’t — that we've heard when folks aren't considering the whole picture.

Telemetry data sent from applications often contains Personally Identifying Information (PII) like names, user IDs, phone numbers, and other information that must be obfuscated before the data is sent to storage or observability tools, in order to be in compliance with corporate or government policies such as HIPAA in the US or the GDPR in the EU.

When it comes to coding and software/app development, two trends are especially appealing to certain business users: low code and no code programming platforms. Let’s take a look at the differences here.

Eight weeks. When someone asks me about the synergies of Cisco + Splunk with regards to full-stack observability, I think about how much we’ve accomplished in just eight weeks. Eight weeks since the close of the acquisition, our teams have already come together to jointly develop, and will deliver, a new capability for enabling observability across the entire digital footprint for both Cisco and Splunk customers.

As a fan of OpenTelemetry, I love to see Cribl meeting customers where they are and helping them get to where they want to be with a vendor-agnostic approach. Where it is not possible or practical to re-instrument a telemetry source, whether an application or infrastructure, the barrier to adopting OpenTelemetry Signals can be daunting.

As we discussed when we rolled out the latest major release of Grafana Loki, we’ve grown the log aggregation system over the past five years by balancing feature development with supporting users at scale. A big part of the latter has been making queries much faster — and that was a major focus with Loki 3.0 too. We’ve seen peak query throughput grow from 10 GB/s in our Loki 1.0 days to greater than 1 TB/s even before 3.0.

Ever found yourself drowning in a sea of log data, struggling to make sense of the overwhelming noise? Or perhaps faced a major system breakdown, only to find that your logs didn’t provide the answers you needed, leaving you in the dark? Effective logging is a critical yet often overlooked aspect of software development and operations, highlighting why logging is important – it’s the foundation upon which observability, troubleshooting, and system maintenance are built.