Skip to content

Logging Enhancements for GCP modules (GONRG-1735, GONRG-1776)

Artem Dobrynin (EPAM) requested to merge gcp-logging-enhancements into master

Type of change

  • Bug Fix
  • Feature

Some enhancements for GCP logging system. Supplies the logs with user id, data-partition-id and correlation id https://gitlab.opengroup.org/osdu/subcommittees/ea/projects/pre-shipping/home/-/issues/50 https://gitlab.opengroup.org/osdu/subcommittees/ea/projects/pre-shipping/home/-/issues/49

Does this introduce a change in the core logic?

  • [NO]

Does this introduce a change in the cloud provider implementation, if so which cloud?

  • AWS
  • Azure
  • GCP
  • IBM

Does this introduce a breaking change?

  • [NO]

What is the current behavior?

The logs are printed in an unparseable inline format.

What is the new/expected behavior?

The logs are printed in JSON format and compatible with GCP Logger.

Have you added/updated Unit Tests and Integration Tests?

No, since it is not required for these changes

Any other useful information

There are two types of logging: for local Spring profile (spring.profiles.active=local) and for any other, incl. default. This was done for better readability while testing locally.

The MR should be merged after osdu/platform/system/lib/cloud/gcp/os-core-lib-gcp!10 (merged)

Merge request reports