Univention Bugzilla – Bug 51738
Slow replication due to prometheus-targets.py
Last modified: 2020-12-28 11:04:41 CET
# univention-app info UCS: 4.3-4 errata617 Installed: admin-dashboard=1.2 dhcp-server=12.0 pkgdb=11.0 prometheus=1.1 prometheus-node-exporter=1.1 ucsschool=4.3 v9 Upgradable: I'm seeing a strange behaviour on a UCS 4.3 that we are trying to update to UCS 4.4. I know that UCS 4.3 is out of maintenance, but the code in question is the same for UCS 4.4, so I assume it's still there. The domain has about 1700 objects that count as "univentionHost" (servers, ipmanagedclients, and so on). As far as I understand, the prometheus-targets.py tries to update the target list of prometheus nodes on every single transaction that occurs for a "univentionHost" object (objectClass=univentionHost). This seems to result in a slowdown of the replication to about 15-20 seconds per transaction on this specific system. All other UCS systems in the domain are fast as always, only the one with the UCS Dashboard installed is that slow. And it results in an unusable logfile with >1700 lines per transaction. Maybe the ldap lookup for prometheus nodes can be optimized? Additionally, some kind of checkbox to actually activate a host as prometheus target would be nice. This way the ldapfilter could be something like '(&(objectClass=univentionHost)(univentionPrometheusTarget=1))'