This message was deleted.
# support
s
This message was deleted.
p
@Prashant Shahi Would you have more insights on this?
hey @Jonathan Berrios thanks for sharing the issue. Seems like you are already getting some help on this in the github issue conversation - https://github.com/SigNoz/signoz/issues/1011 Lets chat more there
👍 1
j
@Prashant Shahi hi here ! can we follow up here please. I added the
kubeletstats
but still doesn't do.
p
@Jonathan Berrios if possible can you please share the otelCollector config?
Have you included
kubeletstats
in the pipeline? It is either that or the SigNoz endpoint is inaccurate or inaccessible.
j
@Prashant Shahi hi ! here it, yes I included it:
Copy code
apiVersion: <http://opentelemetry.io/v1alpha1|opentelemetry.io/v1alpha1>
kind: OpenTelemetryCollector
metadata:
  name: daemonset
  namespace: opentelemetry-collector
spec:
  mode: daemonset
  #hostNetwork: true
  image: otel/opentelemetry-collector-contrib:0.43.0
  securityContext:
    privileged: true
  env:
    - name: K8S_NODE_NAME
      valueFrom:
        fieldRef:
          fieldPath: spec.nodeName
  config: |
    receivers:
      otlp:
        protocols:
          grpc:
          http:

      # Data sources: metrics
      prometheus:
        config:
          scrape_configs:
            - job_name: "otel-collector"
              scrape_interval: 5s
              static_configs:
                - targets: ["localhost:8888"]

      # Data sources: metrics
      hostmetrics:
        scrapers:
          cpu:
          disk:
          filesystem:
          load:
          memory:
          network:
      kubeletstats:
        collection_interval: 60s
        auth_type: "serviceAccount"
        endpoint: "$${K8S_NODE_NAME}:10250"
        insecure_skip_verify: true

    exporters:
      prometheus:
        endpoint: "latest-prometheus-server.default.svc.cluster.local:80"
        namespace: "default"

      otlp:
        endpoint: "my-release-signoz-otel-collector.platform.svc.cluster.local:4317"
        tls:
          insecure: true

    service:
      pipelines:
        metrics:
          receivers: [otlp,hostmetrics,kubeletstats,prometheus]
          processors: []
          exporters: [prometheusremotewrite,otlp]
I should mention, that previous to this, I found out that there wasn't a cluster role neither a cluster role binding for the collector as I installed from the operator CRD. So I worked around that by creating a cluster role binding with wide permissions, for testing only for now until I can get this to work. Please let me know any thoughts you may have. Very appreciated,
I was able to solve this 🙂
🎉 1
p
@Jonathan Berrios That's great to hear! my bad for missing out on the thread discussion.. We are working on the next major releases.