When running the app inside the container, you need to ensure the endpoint where SigNoz is receiving the data is set correctly. This expects the receiver within the container and fails, as the output shows. It is either http://otel-collector:4317 if this dashApp runs as a part of the same n/w or http//<host ip4317> otherwise.
🙏 1
j
John White
02/21/2023, 1:01 AM
Ah, I see! Thank you! So the
Transient error StatusCode.UNAVAILABLE encountered while exporting metrics, retrying in 1s.
error is now gone. However, the "...has been created already" logs is still appearing in the dash container. Additionally, no services is appearing in the Signoz UI even after sending requests in the dash app.
John White
02/21/2023, 1:22 AM
Interesting! If there's an 500 error exception in the instrumented app, services won't load into Signoz. Instead it will show in the
Exceptions
tab in the Signoz UI. Upon fixing this exception, then everything will show up and be tracked properly.
a
Ankit Nayan
02/21/2023, 12:08 PM
@John White services should be listed even if they throw 5xx exceptions. @Vishal Sharma should be able to dig deeper if you are available for a call sometime
👍 1
j
John White
02/22/2023, 4:51 AM
Sounds good to me! I'll reach out to Vishal to see if we can put something on our calendars. Thank you for your support.
👍 2
John White
02/23/2023, 4:17 AM
Just got off a call with @Vishal Sharma. He was a pleasure to interact with and supported me very well. Thank you again 🙂
SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.