https://github.com/entur/cloud-logging

Logging for the JVM
https://github.com/entur/cloud-logging

gcp grpc junit5 logback micrometer slf4j

Last synced: 11 months ago
JSON representation

Logging for the JVM

• Host: GitHub
• URL: https://github.com/entur/cloud-logging
• Owner: entur
• License: eupl-1.2
• Created: 2023-06-28T20:19:32.000Z (over 2 years ago)
• Default Branch: main
• Last Pushed: 2025-03-26T14:39:03.000Z (12 months ago)
• Last Synced: 2025-03-29T22:31:30.450Z (11 months ago)
• Topics: gcp, grpc, junit5, logback, micrometer, slf4j
• Language: Java
• Homepage:
• Size: 970 KB
• Stars: 5
• Watchers: 1
• Forks: 1
• Open Issues: 6
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.txt

Awesome Lists containing this project

README

          
[![Maven Central](https://img.shields.io/maven-central/v/no.entur.logging.cloud/api.svg)](https://mvnrepository.com/artifact/no.entur.logging.cloud)

# cloud-logging

Logging libraries for JVM applications. Goals

 * make developers more productive when developing and maintaining applications

 * keep cloud logging costs within reason

 * help comply with privacy constraints for logging

Features:

 * SLF4J `Logger`-wrapper for additional error levels

 * Plug and play logging scheme

   * Main scope (for production):

     * Machine-readable JSON

   * Test scope (for local development). Log output can be toggled at runtime:

     * Human-readable 'classic' (one-line + ANSI colors, enabled by default), or

     * Human-readable JSON (pretty-printed + ANSI colored), or

     * Machine-readable JSON (single line)

 * Request-response-logging

     * Logbook style output (i.e. inlined in JSON log statements)

     * Additional ANSI coloring for test scope

 * Selective 'on-demand' logging for unexpected web server behaviour

     * capture full logs for problematic requests (i.e. not only WARN or ERROR, but also all sibling INFO log statements). Triggers:

        * HTTP status code

        * Log level (i.e. if ERROR logged, also log sibling INFO statements)

        * Call duration

        * Header present

        * Manual signalling

     * reduce cost of logging considerably

 * Unit testing

   * Always assert against machine-readable JSON 'under the hood', regardless what is printed to console during local development

   * Supported frameworks

     * JUnit 5

 * Correlation-id tracing

This library is mostly based on

 * SLF4J 2

 * Logback + Logback logstash

 * GRPC

   * [Ecosystem](https://github.com/grpc-ecosystem/grpc-spring)

 * [Logbook](https://github.com/zalando/logbook)

Supported web technologies are:

 * Spring web

 * Spring + gRPC

Supported clouds:

 * GCP (Stackdriver)

 * Azure

# License

[European Union Public Licence v1.2](https://eupl.eu/).

# Usage

## Overview

This project contains Spring boot starters which allows for property-based configuration:

 * base configuration (required)

 * request-response-logging (optional)

 * on-demand-logging (optional)

Each Spring Boot starter has a corresponding Spring Boot test starter. The Spring boot test starters enhance the developer experience during local development. 

The above starters are implemented in two flavours:

 * Servlet-based web

 * Netty-based gRPC

## Getting started

See [Getting started with gRPC](guides/gRPC.md) or [Getting started with servlet-based web](guides/web.md). Alternatively, go directly to the [examples](examples).

# Roadmap

 * Replace the correlation-id tracing artifacts with standardized modern equivalents, i.e. span id and so on.

 * Better define and tune request-response logging JSON format

    * Add support for other text formats

    

# See also

 * [logback-logstash-syntax-highlighting-decorators](https://github.com/entur/logback-logstash-syntax-highlighting-decorators)