In this article, learn how to setup application monitoring for Python apps using an open-source solution, SigNoz.

We often get asked, what's the best place to get started with OpenTelemetry - host metrics, traces, or even logs? Hosts Nočnica Mellifera and Pranay will talk about taking your first steps to gathering OpenTelemetry data Below is the recording and an edited transcript of the conversation. Find the conversation transcript below.

This guide is for anyone who is getting started monitoring their application with OpenTelemetry, and is generating unstructured logs. As is well understood at this point, structured logs are ideal for post-hoc incident analysis and broad-range querying of your data. However, it’s not always feasible to implement highly structured logging at the code level.

Join Nočnica Mellifera and Pranay as they discuss architecting and collecting data with the OpenTelemetry Collector. We discuss using Apache Kafka queues to handle OTLP data, and why you probably shouldn't push OTel data straight to Postgres. Below is the recording and an edited transcript of the conversation. Find the conversation transcript below.👇 Nica: Hi everybody! If you're seeing this we're starting up we'll get started in just a moment here.

The team at SigNoz would like to share recent developments released this month that greatly enhance the ability to dynamically query your trace and log data. With these tools anyone can explore complex OpenTelemetry data and gain insight into their stack.

In a recent conversation on our SigNoz community Slack, a user shared their query that asks a deceptively simple question: what is the average time between two spans in a trace? The usefulness of this answer is evident if you think about how often the total trace time does not highlight the time you care about most. This could mean any number of things: that the total trace time of handling a web request might include lots of spans after a satisfying response was sent to the user.

gRPC (Google Remote Procedure Call) is a high-performance, open-source universal RPC framework that Google developed to achieve high-speed communication between microservices. gRPC has Protobuf (protocol buffers) by default which would format or serialize the messages to a specific format that will be highly packed, highly efficient data. By its virtue of being a lightweight RPC, gRPC is suited for many use-cases. gRPC can be considered a successor to RPC, which is light in weight.

In this article, we will implement distributed tracing for a Golang application with three microservices. To implement distributed tracing, we will be using open-source solutions - SigNoz and OpenTelemetry, so you can easily follow the tutorial.

OpenTelemetry can be used to trace Gin applications for performance issues and bugs. OpenTelemetry is an open-source project under the Cloud Native Computing Foundation (CNCF) that aims to standardize the generation and collection of telemetry data like logs, metrics, and traces. Gin is an HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin!

Welcome to the 27th edition of our monthly product newsletter - SigNal 27! Our team shipped the much anticipated Trace and Logs Explorer. With the new Trace Explorer page, SigNoz is the most powerful open-source distributed trace product out there. Let’s dive in to see what humans at SigNoz were up to in the month of July 2023.