https://signoz.io
Join Slack
Hi, using Auto-instrumentation without Sidecar <https://signoz.io/docs/tutorial/opentelemetry-operat...
# support
r
Hi, using Auto-instrumentation without Sidecar https://signoz.io/docs/tutorial/opentelemetry-operator-usage/#auto-instrumentation-without-sidecar and deployed spring-petclinic, but I did not get any logs or monitoring in signoz UI self host. Deployed Signoz services using helm signoz/signoz, cert-manager, and opentelemetry-operator-system. Do I miss anything? Is it enough if I use my own Java application, Auto-instrumentation, and passing inject-java in deployment, or do I still need to set up opentelemetry-javagent in my code?
n
Hey @Rakshith B are you using any custom instrumentation?
r
@Nagesh Bansal if I am passing opentelemetry-javagent in my code still OpenTelemetryCollector and instrumentation should be deployed k8s env?
n
Hey Rakshith, when you're using the opentelemetry-operator and passing the 
inject-java
, the pods will get instrumentation. Ref: https://github.com/open-telemetry/opentelemetry-operator/tree/main?tab=readme-ov-file#opentelemetry-auto-instrumentation-injection
The operator manages: • OpenTelemetry Collector • auto-instrumentation of the workloads using OpenTelemetry instrumentation libraries
r
after deploying signoz/k8s-infra able to get all services logs in ui. and deployed opentelemetry-operator for getting pod monitoring, metrics, graphs and added instrumentation.opentelemetry.io/inject-java: "true" but I don't see anything UI.
n
Please share your Otel-collector, Instrumentation and your java application configs
r
@Nagesh Bansal Hi, would you be available for a quick call, or shall we continue over messages? I’m just looking to clarify a few points and understand gaps from my end.
n
yeah sure
otel-collector:
Copy code
apiVersion: <http://opentelemetry.io/v1alpha1|opentelemetry.io/v1alpha1>
kind: OpenTelemetryCollector
metadata:
  name: otel-collector
spec:
  mode: deployment
  config: |
    receivers:
      otlp:
        protocols:
          grpc:
            endpoint: 0.0.0.0:4317
          http:
            endpoint: 0.0.0.0:4318
    processors:
      batch: {}
    exporters:
      debug: {}
      otlp:
        endpoint: <signoz-otel-collector-svc-endpoint>
 
    service:
      pipelines:
        traces:
          receivers: [otlp]
          processors: [batch]
          exporters: [otlp]
instrumentation resource:
Copy code
apiVersion: opentelemetry.io/v1alpha1
kind: Instrumentation
metadata:
  name: traces-instrumentation
spec:
  exporter:
    endpoint: <otel-collector-svc-ednpoint>
  propagators:
    - tracecontext
    - baggage
    - b3
  java:
    image: ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-java:latest
application-deployment:
Copy code
apiVersion: apps/v1
kind: Deployment
metadata:
  name: java-app
spec:
  selector:
    matchLabels:
      app: java-app
  replicas: 1
  template:
    metadata:
      labels:
        app: java-app
      annotations:
        <http://instrumentation.opentelemetry.io/inject-java|instrumentation.opentelemetry.io/inject-java>: "true"
    spec:
      containers:
      - name: app
        image: java-app:latest
        ports:
        - containerPort: 8080
Hey @Rakshith B try with these configurations
r
sure Thank you
Hi @Nagesh Bansal I tried with above yaml but not getting services in UI
and tried sidecare able to get services in UI only for spring-petclinic which given in document and not working for my own application.
it is working after changing port to 4318
3 Views
Open in Slack
PreviousNext
Powered by

SigNoz Community

SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

Powered by