Operations | Monitoring | ITSM | DevOps | Cloud

The telecommunications world is in the middle of its fourth industrial revolution. Organisations are trying to bring out as many new services as possible to monetise their infrastructure, but despite their modern approach, they still own and maintain legacy — and most importantly — multi-vendor infrastructures. Due to complex organisational structures and decentralised management systems, most responsibilities are divided between multiple departments.

This part 2 of a 3-part series on running ELK on Kubernetes with ECK. If you’re just getting started, make sure to checkout Part 1.

A typical modern DevOps pipeline includes eight major stages, and unfortunately, a release bottleneck can appear at any point: These may slow down productivity and limit a company’s ability to progress. This could damage their reputation, especially if a bug fix needs to be immediately deployed into production. This article will cover three key ways using data gathered from your DevOps pipeline can help you find and alleviate bottlenecks in your DevOps pipeline.

We’re excited to share that the official Elastic Cloud Terraform provider is now available in beta. Operations and SRE teams often rely on Terraform to safely manage production-related infrastructure using methodologies such as infrastructure as code, which allows you to apply peer-reviewed infrastructure changes in an automated and controlled fashion. The provider works with Elasticsearch Service on Elastic Cloud, Elastic Cloud Enterprise, and Elasticsearch Service Private environments.

At the recent Illuminate conference, Dave Sudia from GoSpotCheck shared the process that led them to choosing Sumo Logic for their observability needs.

Aurora, a hosted relational database service available on the Amazon cloud, is a popular solution for teams that want to be able to work with tooling that is compatible with MySQL and PostgreSQL without running an actual MySQL or PostgreSQL database. In order to leverage Aurora’s benefits fully, it’s critical to log and analyze the various types of monitoring data that are available from an Aurora environment.

This blog is part two of Splunk's Sunburst Backdoor response aimed at providing additional guidance to our customers (you can read part one, "Using Splunk to Detect Sunburst Backdoor," by Ryan Kovar). In this blog, we’ll cover how to ingest threat indicators to combat Sunburst Backdoor in Splunk Enterprise Security (ES).

The news of the “Sunburst Backdoor” malware delivered via SolarWinds Orion software has organizations choosing to shut down Orion to protect themselves. This includes several U.S. government organizations following the recent CISA guidance. If you are considering a similar response in your own environment, a critical next step is quickly restoring the lost visibility to the health and operations of your infrastructure.

Sematext Logs is a Log Management-as-a-service. Think of it as your own central location for logs in the cloud. If you prefer or need to keep logs in your own environment instead of shipping it to the cloud Sematext Enterprise, designed to run on your own infrastructure, makes that possible. You can collect logs from any part of your software stack or infrastructure, IoT devices, network hardware, and much more.