hello! :wave: I have deployed SigNoz on our AWS EK...
# support
m
hello! 👋 I have deployed SigNoz on our AWS EKS cluster (service name
signoz
, namespace
monitoring
) and everything’s works fine when sending metrics via http - here’s working config (Spring Boot application):
Copy code
- name: OTEL_LOGS_EXPORTER
  value: "otlp"
- name: OTEL_EXPORTER_OTLP_ENDPOINT
  value: <http://signoz-otel-collector.monitoring.svc.cluster.local:4318>
- name: OTEL_RESOURCE_ATTRIBUTES
  value: service.name=my-monitored-service
the case is, I want to switch to gRPC sending (via port 4317) to be more efficient there I’ve tried just changing port, changing to
https
adding
OTEL_EXPORTER_OTLP_INSECURE=true
property but it all failed - it’s working only via http. Do you have any idea what should I change there?
g
I think that grpc works on grpc protocol grpc://
also your instrumentation need to connect via using the grpc client instead the http one.
m
I’ve check that config:
Copy code
- name: OTEL_LOGS_EXPORTER
  value: "otlp"
- name: OTEL_EXPORTER_OTLP_PROTOCOL
  value: "grpc"
- name: OTEL_EXPORTER_OTLP_ENDPOINT
  value: <grpc://signoz-otel-collector.monitoring.svc.cluster.local:4317>
- name: OTEL_RESOURCE_ATTRIBUTES
  value: service.name=my-monitored-service
just added
OTEL_EXPORTER_OTLP_PROTOCOL
and adjusted protocol and port - it’s not working
I am using most recent client from here:
Copy code
<https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/latest/download/opentelemetry-javaagent.jar>
s
Are there any error logs in spring application?
m
no errors in Spring Boot app