DataDog / ansible-datadog

Ansible role for Datadog Agent
Apache License 2.0
299 stars 222 forks source link

Playbook will not pickup variables for haproxy logs forwarding. #491

Closed bnjeongwo closed 2 months ago

bnjeongwo commented 1 year ago

What task specifically populates /etc/datadog-agent/conf.d/haproxy.d/conf.yaml

bnjeongwo commented 1 year ago

this is how my haproxy vars_file looks. I am not sure why the playbook is not picking up the logs vars to populate /etc/datadog-agent/conf.d/haproxy.d/conf.yaml

---
datadog_checks:
  haproxy:
    init_config:
    instances:
      - url: "https://127.0.0.1:8080/stats"
        tls_verify: xxxx
        tls_ignore_warning: xxxx
  logs:
    - type: file
      path: /var/log/haproxy-traffic.log
      service: my_haproxy_service
      source: haproxy
      sourcecategory: http_web_access
alopezz commented 2 months ago

I took the liberty of editing your comment to use code formatting so that indentation can be looked at (as it's quite critical in yaml). It looks like the whole logs key requires some further indentation, i.e.:

datadog_checks:
  haproxy:
    init_config:
    instances:
      - url: "https://127.0.0.1:8080/stats"
        tls_verify: xxxx
        tls_ignore_warning: xxxx
    logs:
      - type: file
        path: /var/log/haproxy-traffic.log
        service: my_haproxy_service
        source: haproxy
        sourcecategory: http_web_access

I'll be closing this now; note that contacting Datadog support can be much more effective at getting a response for this sort of issue.