summaryrefslogtreecommitdiff
path: root/spec/lib/gitlab/json_logger_spec.rb
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@13-0-stable-eeGitLab Bot2020-05-201-2/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-11-081-0/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-09-171-1/+0
|
* Migrate correlation and tracing code to LabKitan-use-labkitAndrew Newdigate2019-04-181-1/+1
| | | | | | | | | | | | | | | This change is a fairly straightforward refactor to extract the tracing and correlation-id code from the gitlab rails codebase into the new LabKit-Ruby project. The corresponding import into LabKit-Ruby was in https://gitlab.com/gitlab-org/labkit-ruby/merge_requests/1 The code itself remains very similar for now. Extracting it allows us to reuse it in other projects, such as Gitaly-Ruby. This will give us the advantages of correlation-ids and distributed tracing in that project too.
* Revert "Prefer to use correlation-id in logs"Kamil Trzciński2018-12-061-2/+2
| | | | This reverts commit 3560b11922fd180eea5cafd0e763e0e601c5c4ee.
* Prefer to use correlation-id in logsKamil Trzciński2018-12-061-2/+2
| | | | This changes `correlation_id` to be `correlation-id` when passed via jobs
* Log and pass correlation-id between Unicorn, Sidekiq and GitalyKamil Trzciński2018-12-061-0/+6
| | | | | | | | The Correlation ID is taken or generated from received X-Request-ID. Then it is being passed to all executed services (sidekiq workers or gitaly calls). The Correlation ID is logged in all structured logs as `correlation_id`.
* Bring JsonLogger to CEStan Hu2018-07-201-0/+29
This backports a module that was in EE for Geo so that other modules can have structured logging support.