Operations | Monitoring | ITSM | DevOps | Cloud

Latest News

How to Leverage Cribl and Exabeam: Parser Validating

Organizations leverage many different cybersecurity and observability tools for different departments. It’s common to see the IT department using Splunk Enterprise, while the SOC uses Exabeam. Both of these tools use separate agents, each feeding different data to their destinations. Normally this isn’t a problem unless you’re talking about domain controllers. Domain controllers only allow a single agent, meaning you can’t feed two platforms with data.

How to monitor Apache Flink with OpenTelemetry

Apache Flink monitoring support is now available in the open source OpenTelemetry collector. You can check out the OpenTelemetry repo here! You can utilize this receiver in conjunction with any OTel collector: including the OpenTelemetry Collector and observIQ’s distribution of the collector. Below are quick instructions for setting up observIQ’s OpenTelemetry distribution, and shipping Apache Flink telemetry to a popular backend: Google Cloud Ops.

4 Killer Coralogix Tracing Features

Tracing is often the last thought in any observability strategy. While engineers prioritize logs and metrics, tracing is truly the hallmark of a mature observability platform, but it is also the most difficult to implement. Once tracing is in place, engineers typically discover something else – many tracing solutions aren’t particularly feature-rich.

BindPlane OP Build Process - Using Goreleaser

BindPlane OP is written in Go. It is a single http webserver, serving REST, Websocket, and Graphql clients. It includes embedded react applications for serving the user interface. Go provides us with the ability to produce a single binary program that has no external dependencies. The binary is not dynamically linked to external libraries, meaning it is easy to build, deploy, and run on any platform supported by the Go compiler. BindPlane OP officially supports Linux, Windows, and macOS.

3 Pros and Cons of Amazon CloudWatch

Is your organization currently relying on Amazon CloudWatch for log management and log analytics in the cloud? While CloudWatch delivers on many promises for AWS infrastructure monitoring, it isn’t the only log analytics solution – and may not even be your best option. Fast-growing organizations should consider supplementing CloudWatch with innovative alternatives offering better performance at scale, superior cost economics, reduced complexity and enhanced data access in the cloud.

Monitorama 2022: the good, the bad and the beautiful (Part 1)

The summer of 2022 is a strange time to be attending a tech conference. The “Pandemic Pause” has left us all hungry for connection and a little awkward about it. While the world is largely returning to a semblance of comfort with larger public events, COVID is still a real and present threat, something we keep in the backs of our minds all the time.

The Papertrail SaaS Add-On in DigitalOcean Centralizes Everything You Need for Log Management

The SolarWinds® Papertrail™ software as a service (SaaS) Add-On in the DigitalOcean Marketplace is one of the most exciting developments to come out of the DigitalOcean and Papertrail partnership. With the Add-On, developers can seamlessly add the simple yet powerful log management Papertrail is known for to their DigitalOcean infrastructure. In an earlier post, we reviewed how the Add-On helps teams simplify their log management tasks.

Exporting Splunk Data at Scale: See a Need, Fill a Need

The Core Splunk platform is rightfully recognized as having sparked the log analytics revolution when viewed through the lenses of ingest, search speed, scale, and usability. Their original approach leveraged a MapReduce approach, and it still stores the ingested data on disk in a collection of flat files organized as “buckets.” These immutable buckets are not human-readable and largely consist of the original raw data, indexes (.tsidx files), and a bit of metadata.

Network as Code Explained: How Ansible & Automation Support Agile Infrastructure

When considering application source code, the way you maintain consistency throughout environments is mostly straightforward. You write application code, commit it to source control, and then build, test and deploy via a CI/CD pipeline. Since the application is defined by the source code living in source control, the build will be identical in all environments to which it’s deployed. But what about the infrastructure on which an application runs?