Agent 7.16.0 cannot parse non-semantic nginx version
See original GitHub issueAfter upgrading DataDog agent to 7.16.0 nginx integration stopped working.
Agent Log:
Dec 18 15:42:50 nginxproxy agent[29323]: 2019-12-18 15:42:50 EST | CORE | ERROR | (pkg/collector/python/datadog_agent.go:116 in LogMessage) | nginx:17d65b5a97c80644 | (core.py:45) | Unable to transform `version` metadata value `nginx`: Version does not adhere to semantic versioning
nginx -v:
nginx version: nginx/1.13.9 (Ubuntu)
Nothing changed in nginx.d/conf.yaml
except status url:
- nginx_status_url: http://localhost:8080/stub_status/
datadog-agent version:
Agent 7.16.0 - Commit: 3e13b77 - Serialization version: 4.15.0 - Go version: go1.12.9
Worked fine with version Agent 6.15.1-1
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Install and Configure NGINX Agent | NGINX Management Suite
Follow the instructions in this guide to install and configure the NGINX Agent on your data plane systems.
Read more >How NGINX Amplify Agent Works
NGINX Amplify Agent is a compact application written in Python. Its role is to collect various metrics and metadata and send them securely...
Read more >Set up Metrics Collection | NGINX Controller
The Agent is able to automatically find all relevant NGINX configuration files, parse them, extract their logical structure, and send the associated JSON ......
Read more >Configure the NGINX Controller Agent
Customize the NGINX Controller Agent configuration. ... If the Agent cannot determine the hostname, you can set the hostname in the agent.conf file....
Read more >Release Notes 3.22.0 | NGINX Controller
Upgrade Considerations · After upgrading NGINX Controller, make sure to upgrade the NGINX Controller Agent too. Caution: · If you're upgrading ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
My bad, metrics are actually sent. There was a delay in them showing in a dashboard which made me think version parsing was a problem.
Thanks for the feedback. I was wondering if it was possible for you to set
server_tokens on
on thenginx_status
location. This should allow the check to retrieve the version, and hopefully not leak it on others.