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

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

Closed
bnjeongwo opened this issue Jun 17, 2023 · 2 comments
Closed

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

bnjeongwo opened this issue Jun 17, 2023 · 2 comments

Comments

@bnjeongwo
Copy link

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

@bnjeongwo
Copy link
Author

bnjeongwo commented Jun 21, 2023

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
Copy link
Contributor

alopezz commented Jul 19, 2024

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.

@alopezz alopezz closed this as completed Jul 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants