7.36.0 breaks mysql.net.connections, reports bogus values
See original GitHub issue7.36.0 changes the behavior of mysql.net.connections
in a way that was probably unintentional. 7.36.0 reports the Connections status variable as a raw value, but that poses a problem because Connections is cumulative. This is breaking change from 7.35.2, which reported the delta. That’s resulting in completely broken metrics when updating to 7.36.0:
I originally reported this at https://github.com/DataDog/datadog-agent/issues/12150, but I’m moving it here because it’s technically an issue with the MySQL check.
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Upgrading from 7.35.2-1 to 7.36.0-1 breaks MySQL checks, ...
Preliminary bug report. Upon updating today, Datadog immediately started reporting about 21M conn/s for avg:mysql.net.connections, ...
Read more >4.5 Connector/NET 8.0 Connection Options Reference
This chapter describes the full set of MySQL Connector/NET 8.0 connection options. The protocol you use to make a connection to the server...
Read more >4.3 Handling Connection Errors
NET application. When there is an error connecting, the MySqlConnection class will return a MySqlException object. This object has two properties that are ......
Read more >4.22 Troubleshooting Problems Connecting to MySQL
Make sure that the server has not been configured to ignore network connections or (if you are attempting to connect remotely) that it...
Read more >8.4 Connector/ODBC Errors and Resolutions (FAQ)
This error can be raised by a number of different issues, including server problems, network problems, and firewall and port blocking problems. For...
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
Hey @Zenexer, thanks again for reporting this issue and we apologize for the inconvenience. We just reverted the change that affected the metric (https://github.com/DataDog/integrations-core/pull/12088) and we’re currently working on a new release for 7.36 that will include this fix.
Hey @Zenexer, just following up with this issue. We’re in the process of rolling out
Agent v7.36.1
which will include this fix. However, please note, if you are using DBM (dbm: true
), you will not see an immediate change because we have to make some additional changes in our pipeline amongst other processes. This process is expected to take approximately 1 week. Thanks again for your patience!