Operations | Monitoring | ITSM | DevOps | Cloud

Traditionally, when monitoring or troubleshooting active incidents, engineers access logs directly on the source system. However, modern IT environments are now too complex, and engineers can no longer manage and analyze logs effectively this way. With the adoption of microservices and the use of cloud-native infrastructure, it’s no longer feasible.

Moving to Splunk Cloud Platform has a lot of benefits, including flexibility, agility, and scalability. However, we understand that migrating to cloud is not a trivial task and can also bring up security concerns especially when it comes to having your data traverse the internet.

This article will give you a quick overview of some of the key attributes you should know in order to get started with leveraging the OpenTelemetry collector for your next telemetry project. As an integral component of any project that involves distributed tracking, the OpenTelemetry Collector plays an important role. Simply put, it is helpful to know that the collector itself is a data pipeline service that collects telemetry data.

Over the last 15 years, digital technology has fundamentally changed the way businesses operate. Every industry, from retail and hospitality to banking and airlines, has not only had to adjust to a world where customers increasingly rely on digital experiences, but they also have to build and manage the platforms where these experiences take place.

One thing that adds value to a business’s ecommerce presence is the ability for customers to easily find physical stores with an interactive map. Store locators can be built quite rapidly — all you need to place them on a map is geographic location in latitude and longitude. In this post, I’ll outline the pieces needed to put together a proof-of-concept store locator that could later be added to an ecommerce website.

Observability is a methodology that you incorporate into your enterprise architecture to provide greater visibility into what is happening. It helps us determine the states of the system from their external outputs and allows technicians to identify bottlenecks, predict issues and mitigate them. As the architectures of IT systems are becoming more complex and distributed we use observability to meet the need to measure their internal states.

Observability is a hot topic in the IT world these days. It is oftentimes discussed through the lens of the “three pillars of observability”: Logs, Metrics and Traces. Indeed these telemetry signal types help us understand what happened, where it happened and why it happened in our system.

In my last blog post, Building a Cost-Effective Full Observability Solution Around Open APIs and CNCF Projects, we introduced using ChaosSearch in combination with the most popular open source front- and back-ends in the application observability space. In case you missed it, the TL;DR version is that you can use a variety of open source projects and open API-based components to build the best-of-breed observability stack of your choice rather than relying on expensive, all-in-one solutions.