GitLab

Run GC major collection after each request

See merge request gitlab-org/gitlab-exporter!131

We found that this has a positive impact on memory use and gitlab-exporter is not a high-traffic system so the performance hit should be negligible.

Update rubocop from 0.42.0 to 0.93.1

See merge request gitlab-org/gitlab-exporter!129

Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>

Update Ruby from 2.3 to 2.7

See merge request gitlab-org/gitlab-exporter!128

Allow to specify which server to use

See merge request gitlab-org/gitlab-exporter!127

Also updates Bundler from 1.17.3 to 2.1.4
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>

If not specified, default to WEBRick

Update bloat queries

See merge request gitlab-org/gitlab-exporter!125

Update the bloat queries from their latest upstream versions.
Signed-off-by: Ben Kochie <bjk@gitlab.com>

Fix /database_bloat endpoint

See merge request gitlab-org/gitlab-exporter!124

This was missing the logger introduced in !121.

Reduce CPU utilization of row count query

Closes #75

See merge request gitlab-org/gitlab-exporter!123

Previously, scraping the /database metrics used a significant amount of
CPU because each query would rebuild the PG to Ruby data type map. We
now memoize this map so we only need to build this map once.

Closes https://gitlab.com/gitlab-org/gitlab-exporter/-/issues/75

Enable security-related jobs in CI

See merge request gitlab-org/gitlab-exporter!122

The `bundle install` call in the default
specification broke the security related jobs as
bundler is not available in the Docker image for
these jobs.

Log database errors

Closes #72

See merge request gitlab-org/gitlab-exporter!121

Because we dynamically create these probes, we just allow these unused
arguments.

Previously all `PG::ConnectionBad` errors were quietly swallowed. We now
pass along a logger so that we can see when these errors occur.

Closes https://gitlab.com/gitlab-org/gitlab-exporter/-/issues/72

Fix application_settings JOIN condition for CiBuildsProbe

Closes #71

See merge request gitlab-org/gitlab-exporter!119

After https://gitlab.com/gitlab-org/gitlab/-/merge_requests/29981, we cannot assume an application_settings
with ID=1 exists. But we know that there will only be one record in that table, so we can change the JOIN
condition to TRUE safely.

Fixes #71

Use Licenses count as an indicator of an EE installation

Closes #71

See merge request gitlab-org/gitlab-exporter!118

Fixes #71

Add Secure scanning tools

See merge request gitlab-org/gitlab-exporter!117

Remove usage of ghost column

See merge request gitlab-org/gitlab-exporter!116

Ghost column was migrated to user_type column and will be removed soon. So we need to update exporter to rely on user_type only before we actually remove ghost column from DB.

Bump version to 7.0.3

See merge request gitlab-org/gitlab-exporter!115

Replace `bot_type` with `user_type`

See merge request gitlab-org/gitlab-exporter!114

- Removes `bot_type` as a field in the database query because it was
  removed from the schema in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/27076

Related https://gitlab.com/gitlab-org/gitlab-exporter/-/issues/70Signed-off-by: Robert Marshall <rmarshall@gitlab.com>

- Bumps the gem version to 7.0.3

Related https://gitlab.com/gitlab-org/gitlab-exporter/-/issues/70Signed-off-by: Robert Marshall <rmarshall@gitlab.com>