Operations | Monitoring | ITSM | DevOps | Cloud

Learn more about event streaming architecture with Apache Kafka® and Apache Flink®, landing data into real-time analytics data warehouse ClickHouse®.

Already using Apache Kafka®? Here’s why you should be analyzing your streaming data, not just moving it around.

HostedGraphite provides a complete infrastructure and application monitoring platform from a suite of open-source monitoring tools. Use Hosted Graphite and view all required metrics on beautiful dashboards in real time. Hosted Graphite offers a wide range of tools, add-ons, and plugins which make it possible to measure, analyze, and visualize large amounts of data about your applications with ease.

It is getting spooky out there, folks! Every year on October 31, we don our spookiest (or silliest) garb, an evolution of old practices where people would dress up to ward off ghouls, goblins and all manner of things that go bump in the night. After all, people believed these pesky spirits stirred up trouble. While pieces of this spooky tradition persist, just a few other things have changed in the past 2,000 years. For starters, we are a digital society.

If you’re unfamiliar with observability, you might think an “observability engineer” is just a fancy way to say data admin — but while observability engineers often work with data admins, they work toward different goals. Data admins monitor information to identify and fix known security issues. Observability engineers work to provide a complete picture of all the data a company aggregates and what it means for a business.

Raise your hand if you enjoy being kicked out of the application you were working on for an unexpected security patch! No one? We can wait … Really, no one? Okay, we figured. And we’re not surprised. Jamie Whalen, host of the Everywhere Workplace Podcast, recently sat down with Steve Brasen, Research Director for Enterprise Management Associates, to talk about the perceived conflict between Digital Employee Experience (DEX) and security.

The internet of things is one of my favorite topics. IOT enables low-powered connected devices that opens gateways from the digital to the real world. While I love tinkering away with an Arduino sketch and the latest Espressif or Arduino board, there is always an air of frustration when trying to build out what at first seems like simple functionality using one of these “smart devices” because of the limited view we have into their operations.

Typically, startup founders and executives must meet with their board of directors each quarter to review the progress of the company. They may talk about broad topics such as total costs and total revenue, and use these numbers as a guide to determine which moves the company should make in the near future. Often missing from the conversation, however, is a clear and detailed discussion of SaaS metrics.

There is a famous quote that goes like this…‘For every minute spent organizing, an hour is earned.’ At least in the world of incident response, nothing is more apt than this. Digital infrastructure these days is made up of multiple services, an outage could result from either one impacted service or multiple impacted services. So it's essential to have a catalog of all the services along with the point of contact (service owner) responsible for maintaining it.

This article was originally published in The New Stack and is reposted here with permission. Working with geo-temporal data can be difficult. In addition to the challenges often associated with time-series analysis, like large volumes of data that you want real-time access to, working with latitude and longitude often involves trigonometry because you have to account for the curvature of the Earth. That’s computationally expensive. It can drive costs up and slow down programs.