Operations | Monitoring | ITSM | DevOps | Cloud

The Covid-19 pandemic has had an incredible impact on the world as nations work to keep their economies moving, secure the health and welfare of their citizens through social distancing, testing, and an immediate transition to remote work and classrooms. The world is adopting these measures while anxiously waiting for the great scientific institutions and private enterprises to test and deliver a vaccine to eradicate the SARS-CoV-2 coronavirus we know as Covid-19.

Kubernetes (k8s) enables you to efficiently orchestrate container management, in the cloud or on-premises. As a whole, k8s provides many benefits, including features for self-healing, automated rollouts and rollbacks, load distribution, and scalability. However, k8s is a highly complex platform and requires extensive configuration.

Canonical is proud to announce the general availability of OSM release EIGHT images in it’s Charmed OSM distribution. As of Release SEVEN, OSM is able to orchestrate containerised network functions (CNFs) leveraging Kubernetes as the underlying infrastructure for next-generation 5G services. Release EIGHT follows the same direction and brings new features that allow for the orchestration of a broader range of network functions and production environments.

Isn’t all logging pretty much the same? Logs appear by default, like magic, without any further intervention by teams other than simply starting a system… right? While logging may seem like simple magic, there’s a lot to consider. Logs don’t just automatically appear for all levels of your architecture, and any logs that do automatically appear probably don’t have all of the details that you need to successfully understand what a system is doing.

Simple, yet powerful metrics to determine the health and protection status of your Spectrum Protect environment in a single pane of glass.

After my last blog around sending Github Data to Splunk via Webhooks, I received a healthy amount of feedback that I want to address here. I learned that (unsurprisingly) a lot of customers are curious about, or dependant on, other cloud platforms out there. In fact, I heard directly from some customers who specifically cannot use any other cloud platforms than one in particular that was not highlighted in my last blog.

In case 2020 wasn’t dystopian enough, here’s some more unbelievable news. On July 15, 2020, social media giant Twitter admitted it fell victim to a security breach. The attackers targetted 130 Twitter accounts, including several belonging to high-profile individuals such as elected officials; former president Barack Obama; and business leaders including Bill Gates, Jeff Bezos, and Elon Musk.

If you are familiar with OpenTracing and OpenCensus, then you have probably already heard of the OpenTelemetry project. OpenTelemetry merges the OpenTracing and OpenCensus projects to provide a standard collection of APIs, libraries, and other tools to capture distributed request traces and metrics from applications and easily export them to third-party monitoring platforms.

Maintaining business continuity is both more difficult and more important than ever in the era of COVID-19. Typically, IT departments evolve their approaches and technologies over time to meet the needs of customers. But that approach may soon be outdated thanks to the global pandemic.

Jaeger primarily supports two backends: Cassandra and Elasticsearch. Here at Grafana Labs we use Scylla, an open source Cassandra-compatible backend. In this post we’ll look at how we run Scylla at scale and share some techniques to reduce load while ingesting even more spans. We’ll also share some internal metrics about Jaeger load and Scylla backend performance. Special thanks to the Scylla team for spending some time with us to talk about performance and configuration!