You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found this tool and it fit my usecase of generating simple synthetic traces to help with setting up the rest of the infrastructure without getting bogged down with other details. It's strange how many demos focus on a huge amount of services and etc. but there's not a lot of focus on more scaled down simulators. It helped with a couple of tests and to get started on a PoC so thanks for that!
I was trying to setup an NGINX ingress on k8s to be able to ingest remote traces and along the way had a fair share of 400 and other HTTP errors but I managed to fix those.
However, then I went down multiple rabbit holes trying to validate my TLS setup and various other configurations.
With insecure connection the service worked fine and sent traces, when I wanted to test with the secure option I got errors like this: 2024/10/25 15:07:51 traces export: Post "https://httptest.xyz.com:443/v1/traces": tls: failed to verify certificate: x509: certificate signed by unknown authority
I racked my brain and rechecked my other configs in case there was something else but in the end I came to a conclusion that maybe this tool just doesn't recognise Let's Encrypt CA and hence nothing I did could get me to enable the secure option.
I tried another GO based tool and there the TLS config seemed to work fine.
Did I miss something or is this a bug?
The text was updated successfully, but these errors were encountered:
Hey,
I found this tool and it fit my usecase of generating simple synthetic traces to help with setting up the rest of the infrastructure without getting bogged down with other details. It's strange how many demos focus on a huge amount of services and etc. but there's not a lot of focus on more scaled down simulators. It helped with a couple of tests and to get started on a PoC so thanks for that!
I was trying to setup an NGINX ingress on k8s to be able to ingest remote traces and along the way had a fair share of 400 and other HTTP errors but I managed to fix those.
However, then I went down multiple rabbit holes trying to validate my TLS setup and various other configurations.
With insecure connection the service worked fine and sent traces, when I wanted to test with the secure option I got errors like this:
2024/10/25 15:07:51 traces export: Post "https://httptest.xyz.com:443/v1/traces": tls: failed to verify certificate: x509: certificate signed by unknown authority
I racked my brain and rechecked my other configs in case there was something else but in the end I came to a conclusion that maybe this tool just doesn't recognise Let's Encrypt CA and hence nothing I did could get me to enable the secure option.
I tried another GO based tool and there the TLS config seemed to work fine.
Did I miss something or is this a bug?
The text was updated successfully, but these errors were encountered: