Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Beyla in kubernetes detects itself as unknown_service:beyla #1467

Open
gouthamve opened this issue Dec 17, 2024 · 0 comments
Open

Beyla in kubernetes detects itself as unknown_service:beyla #1467

gouthamve opened this issue Dec 17, 2024 · 0 comments
Labels

Comments

@gouthamve
Copy link
Member

Image Image

This is running with the following config:

  attributes:
    kubernetes:
      cluster_name: office
      enable: true
    select:
      beyla_network_flow_bytes:
        include:
        - k8s.src.owner.type
        - k8s.dst.owner.type
        - direction
  discovery:
    services:
    - k8s_namespace: .
  filter:
    network:
      k8s_dst_owner_name:
        not_match: '{kube*,*jaeger-agent*,*prometheus*,*promtail*,*grafana-agent*}'
      k8s_src_owner_name:
        not_match: '{kube*,*jaeger-agent*,*prometheus*,*promtail*,*grafana-agent*}'
  internal_metrics:
    prometheus:
      path: /internal/metrics
      port: 9090
  otel_traces_export:
    endpoint: http://k8s-monitoring-alloy.monitoring.svc.cluster.local:4317/
  prometheus_export:
    features:
    - application
    - network
    - application_service_graph
    - application_span
    path: /metrics
    port: 9090
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant