This message was deleted.
# general
s
This message was deleted.
p
Hey @User Let me check this. Will revert soon
@User I don't think you need access_token if you are running signoz backend yourself. This blog mentions how you can run a sample go app -> https://signoz.io/blog/monitoring-your-go-application-with-signoz/ Can you try commenting out the blocks needing signoz access token in the instrumentation. I think it should work then. I will also confirm with my team though
v
Do u support TCP/UDP based applications
Because we have many applications which are TCP and UDP based
p
@User Can you give an example of a UDP based application which you have - and typical metrics you would want to monitor there?
v
This is video/audio conferencing, which will be sent on UDP. We would want to monitor metrics such as. 1. rate of packets 2. total packets sent/received 3. No of received and sent ports
p
Ok. Got it. let me check Reg, SigNoz access token.. confirmed with my team that you don't need them. The instrumentation will work even if you don't provide the token. They are just env variables @User
v
but its been getting used
Copy code
headers := map[string]string{
        "signoz-access-token": signozToken,
      }
Copy code
exporter, err := otlp.NewExporter(
        context.Background(),
        otlpgrpc.NewDriver(
          secureOption,
          otlpgrpc.WithEndpoint(collectorURL),
          otlpgrpc.WithHeaders(headers),
a
@User, It's just headers. If you self-host these headers will be ignored. Though would be nice not to have this in FOSS version. Will update the docs
@User OpenTelemetry takes care of instrumentation. If you tell me the code language and libraries you use for udp requests, I shall look into OpenTelemetry to check. On the other hand, you can always create such metrics using OpenTelemetry sdks.
v
we use golang
@User is the Dev Lead here, @User if you help us here. we both will take it ahead from here
p
ok - we will get this checked @User
a
@User @User Do you use docker to deploy your applications? cadvisor gives some network stats about each container. That might be relevant with metrics like
container_network_udp_usage_total
and various other transitted, received and dropped packet counts about each container. We are building metrics ingestion pipeline which can ingest prometheus compatible metrics. Should be out in a month.
v
we are using GKE to deploy application
@User we integrated Signoz for one of our applications, but we dont see errors getting reported on the dashboard.
@User
a
@User @User how are the errors generated? Are the grpc apis throwing error?
a
Hi