Skip to content

MDBF-1174: Remove Zabbix checks#989

Open
RazvanLiviuVarzaru wants to merge 1 commit into
MariaDB:devfrom
RazvanLiviuVarzaru:MDBF-1174-zabbix-bb
Open

MDBF-1174: Remove Zabbix checks#989
RazvanLiviuVarzaru wants to merge 1 commit into
MariaDB:devfrom
RazvanLiviuVarzaru:MDBF-1174-zabbix-bb

Conversation

@RazvanLiviuVarzaru

Copy link
Copy Markdown
Collaborator

Zabbix has a BB Accept Builds metric which was used only for scheduling s390x builds.

Due to resource constraints the s390x workers accept one build at a time -> see worker_locks.yaml -> using the zabbix metric has no additional benefit.

Remove the surrounding zabbix code since we're moving to Prometheus. For now I don't see the need of a Prometheus equivalent for the metric because we already have 3 control mechanisms for the workers load:

  • locks :: used by dockerlatent masters
  • max_builds :: used by non-latent masters
  • scheduling based on worker available CPU's count :: used by master-migration

Zabbix has a `BB Accept Builds` metric which was used only for scheduling s390x builds.

Due to resource constraints the s390x workers accept one build at a time -> see `worker_locks.yaml`
-> using the zabbix metric has no additional benefit.

Remove the surrounding zabbix code since we're moving to Prometheus.
For now I don't see the need of a Prometheus equivalent for the metric
because we already have 3 control mechanisms for the workers load:
- locks :: used by dockerlatent masters
- max_builds :: used by non-latent masters
- scheduling based on worker available CPU's count :: used by master-migration
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant