Python Instrumentation - Monitor your Python application using OpenTelemetry and SigNoz

In this video, learn how to set up application monitoring for Python apps using an open-source solution, SigNoz and OpenTelemetry.

Tracing your application can give the much-needed context required to troubleshoot performance issues. OpenTelemetry is an open-source project that can help you set up an observability framework for your cloud-native applications.

In this tutorial, we will use SigNoz as our backend analysis tool. SigNoz is a full-stack open-source APM tool that can store and visualize the telemetry data collected with OpenTelemetry. It is built natively on OpenTelemetry and works on the OTLP data formats.

More about SigNoz:

SigNoz - Monitor your applications and troubleshoot problems in your deployed applications, an open-source alternative to DataDog, New Relic, etc. Backed by Y Combinator.

SigNoz helps developers monitor applications and troubleshoot problems in their deployed applications. SigNoz uses distributed tracing to gain visibility into your software stack.

If you need any clarification or find something missing, feel free to raise a GitHub issue with the label documentation or reach out to us at the community slack channel.

SigNoz Instrumentation with OpenTelemetry blogs:

TIMESTAMPS
00:00 Monitor your Python application using OpenTelemetry and SigNoz
00:27 Cost of a Millisecond
01:28 Agenda of the Video
02:24 Install SIgNoz
03:37 Prerequisites
03:41 Clone Sample flask App
04:51 test run the app
06:05 Install dependencies for Flask app
06:41 Install application specific OpenTelemetry packages
07:09 Setup Environment Variables setup (IP of SigNoz)
08:14 Generate Telemetry Data by interacting with Flask App
08:47 SigNoz Dashboard for Metrics and Traces
09:40 Trace Details using Flame Graphs and Gantt Charts
10:38 Reach out to us on Slack

[wmdevsec]

hi Priyansh, nice explanation, it's working. Only thing if mongodb serverice went, then flask application stopped working, however this I cann't get in traces that Mongodb service down, waiting for comments.