Refactor of db/table limits
General
Escalation
General
Escalation
Description
How to test
Test
limit for MySQL tables and autodiscovery in PG DB and Mongo DB collections
automation needed for autodiscovery
How to document
None
relates to
Activity
Show:
Done
Details
Details
Assignee
Jiří ČtvrtkaReporter
Jiří ČtvrtkaPriority
MediumLabels
Needs QA
No
Needs Doc
No
Planned Version/s
Fix versions
Story Points
4
Due date
Jan 31, 2025
Parent
Smart Checklist
Open Smart Checklist
Smart Checklist
Open Smart Checklist
Created October 30, 2023 at 8:38 AM
Updated January 31, 2025 at 2:47 PM
Resolved December 16, 2024 at 10:41 AM
Current implementation:
1. MySQL and PG using Service Info Broker. MongoDB doesnt. MongoDB should be reworked to use Service Info Broker too - There is no use for MongoDB with the Service Info Broker yet. The CollectionsLimit is handled by the exporter itself.
2. Table limits for MySQL is saved as property on agent. In case of PG and MongoDB similar fields are saved in "PostgresqlOptions" and "MongoDbOptions" structures on agent. MySQL should be reworked to save table limits in MySQLOptions.
3. Align other parts of code related to this
4. Migrate MySQLOptions, PostgreSQLOptions, MongoDBOptions database columns to JSON type. Also ensure consistent naming of those. For example, `mongodb_tls_options` should be `mongodb_options`, like the other two columns.