Update error message for defaultListenerFactory

See merge request !36

Error string should not be capitalized or end with punctuation.

Monitoring endpoint

See merge request !35

This service includes support for

1. OpenMetrics
1. Pprof
1. The `gitlab_build_info` metric

Add incoming HTTP service metrics to LabKit

See merge request !30

This changes adds standardised prometheus metrics middlewares to LabKit.

The middleware will expose the following metrics:

* in_flight_requests
* requests_total
* request_duration_seconds
* request_size_bytes
* response_size_bytes
* time_to_write_header_seconds

Switch workhorse compatibility to `go mod`

See merge request !34

Update code quality job

See merge request !33

Use the new template provided by GitLab
https://docs.gitlab.com/ee/ci/examples/code_quality.html. By default the
stage is set to `test` which is not a stage that we have available.
Override the stage to `verify`.

Filter title, description, text, and body from logs

See merge request !31

These can also contain sensitive content.

Add a color formatter

See merge request !29

This option is necessary to support the functionality currently provided
by Workhorse.

Add an HTTP server access logger middleware

See merge request !22

Adds an access logger middleware for consistent access logging across
components.

Updated logging API

See merge request !28

This change delegates the logging API to Logrus. This means a far
more user-friendly API, since developers only need to including one
package, but the API does not need to wrap or unwrap calls, as types
are aliased for the logrus package.

Ensure backwards compatibility by compiling client applications

See merge request !26

This is done by checking out the master branch of Workhorse and
Gitaly, updating to the current branch of Labkit and ensuring that the
code still compiles.

If an API change that is not backwards compatible is introduced, these
tests will fail.

Listen for `SIGHUP` signals and reopen log file on signal.

See merge request !23

When logging to a file, sending a SIGHUP to the process will reopen
the log file. If an error occurs, the process will attempt to log it
through the main logger or alternatively stderr.

Restore backwards compatibility in library.

See merge request !25

The `raven.SetExtra` method was accidentally removed. Although this
functionality is deprecated, it is required for backwards compatability.

Add additional mask URL tests from Workhorse

See merge request !27

Adds masking functionality

See merge request !21

Package mask provides functionality to provide non-reversible masking
for sensitive data in the GitLab application.

Is provides the ability to determine whether or not a URL parameter or
Header should be considered sensitive.

Additionally, it provides masking functionality to mask sensitive
information that gets logged via logging, structured logging, sentry
and distributed tracing.

Zeger-Jan van de Weg authored 5 years ago and Andrew Newdigate committed 5 years ago

Add labkit logger package

See merge request !20

Unlike some of the other functionality provided by Logkit,
the logging functionality does not wrap an underlying log provider.

Why not? Because, in a past life, I worked as a Java developer and
therefore understand that log wrappers will bring you nothing but pain
and unhappiness.

Instead of being a log wrapper, this functionality encourages
applications to use logrus. Logrus is already widely used in GitLab.

What benefit does this functionality add:
* Consistent configuration of logrus
* Importantly, this functionality allows labkit itself to write logs.
  * This will allow us to add better logging, as well as standardised
    access loggers, exception loggers etc

Co-authored-by: Zeger-Jan van de Weg <zegerjan@gitlab.com>

Handle err immediately for sentry DSN setup

Closes #2

See merge request !18

raven.SetDSN returns an err which is not being checked just returned at
the end. It might not be a problem right now but in the case when the
function gets bigger the `err` var can get shadowed.

There is also no point in continuing setting up errortracking if we fail
to set up sentry.

closes #2

Feat: Add essentials to errortracking

See merge request !19

feat(raven): move helper functions from workhorse

See merge request gitlab-org/labkit!12

Defer setting of response header until after client responds

See merge request !17