GitLab

Remove ci_repeated_commands_builds metric

Closes #77

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

The column ci_builds.commands has been removed from Rails and has
been deprecated for long before that, thus this metric is no longer functioning.

Related to https://gitlab.com/gitlab-org/gitlab/-/merge_requests/54564

Fixes https://gitlab.com/gitlab-org/gitlab-exporter/-/issues/77

Remove info about process probe

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

Add ruby GC stats probe

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

Notify code producing `process_*` metrics is obsolete

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

We remove `process_*` metrics probing from Omnibus, so this code should
be no longer needed.

Optimise `Sidekiq probe`

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

Make Puma an explicit dependency

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

This also bumps Puma from v4.x (which was bundled by Sinatra) to 5.1.1.

Optimise `DB probe`

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

This makes:
- To re-use Redis connection instead of openning
  it each time a probe is requested and leaking
  the connection pool

This makes to scrape current Ruby process
of `GC.stat` to be able to monitor the memory
pressure impact.

This fixes two memory/CPU aspects of DB probe:

- connection re-use across different probes
  where the same connection string is used
- the type mapping is done only once

This improves execution and memory usage by:

- about `4M-6M` less of memory allocation due
  to type-mapping re-use
- about `30%` execution time due to more efficient
  connection re-use

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.