mirror of
https://github.com/SigNoz/opentelemetry-python-example.git
synced 2025-07-25 08:19:54 +08:00
updated image address
This commit is contained in:
@ -24,17 +24,17 @@ In this tutorial series, we will be using SigNoz Cloud to visualize everything t
|
||||
After you sign up and verify your email, you will be provided with details of your SigNoz cloud instance. Once you set up your password and log in, you will be greeted with the following onboarding screen.
|
||||
|
||||
|
||||

|
||||

|
||||
|
||||
Since we will be following instructions from the tutorial, you can skip onboarding by clicking on the SigNoz logo.
|
||||
|
||||
You will see the below screen:
|
||||
|
||||

|
||||

|
||||
|
||||
For sending data to SigNoz cloud, you will be needing details like ingestion key and region. You can find them under `Ingestion Settings` under `Settings`.
|
||||
|
||||

|
||||

|
||||
|
||||
## **Self-Host SigNoz**
|
||||
|
||||
|
@ -98,11 +98,11 @@ Interact with the Flask application to generate tracing data and send it to SigN
|
||||
|
||||
Once you've created some dummy telemetry by interacting with your application, you will be able to find your application under the `Services` tab of SigNoz.
|
||||
|
||||

|
||||

|
||||
|
||||
You can click on the application to see useful application metrics like latency, requests rates, error rates, apdex score, key operations, etc.
|
||||
|
||||

|
||||

|
||||
|
||||
## Additional: Troubleshooting if you can’t see data in SigNoz
|
||||
|
||||
|
@ -77,7 +77,7 @@ Interact with the Flask application to generate tracing data and send it to SigN
|
||||
|
||||
Once you've created some dummy telemetry by interacting with your application, you will be able to find your application under the `Services` tab of SigNoz.
|
||||
|
||||

|
||||

|
||||
|
||||
|
||||
## Next Steps
|
||||
|
@ -196,11 +196,11 @@ python lesson-4/app.py
|
||||
|
||||
Once you run the application and add a task, you will be able to see it in SigNoz.
|
||||
|
||||

|
||||

|
||||
|
||||
You can see your span in the trace detail view too which will show how the request flowed and how much it took for the `add_task` operation.
|
||||
|
||||

|
||||

|
||||
|
||||
## Next Steps
|
||||
|
||||
|
@ -112,19 +112,19 @@ python lesson-5/app.py
|
||||
|
||||
Let's suppose you add 6 tasks in your to-do application.
|
||||
|
||||

|
||||

|
||||
|
||||
You can go to `Dashboards` in SigNoz and create a new panel to monitor the number of tasks in your to-do application using the `todo_counter` metric.
|
||||
|
||||

|
||||

|
||||
|
||||
You can create a value panel type and monitor the number of tasks being created.
|
||||
|
||||

|
||||

|
||||
|
||||
You can also set alerts on metrics based on your use-case directly from these panels.
|
||||
|
||||

|
||||

|
||||
|
||||
|
||||
## Next Steps
|
||||
|
Reference in New Issue
Block a user