[ONBOARDING] loki

[lucabello]

Image name

loki

Image repository

https://github.com/canonical/loki-rock

Image type

ROCK

Maintainer agreement

• I agree to follow this project's Code of Conduct

• I understand and acknowledge the CONTRIBUTING guidelines and Image Maintainer Agreement

• This image is either a ROCK or a Docker image which already exists in the 'ubuntu' namespace

• I agree to be the image's Maintainer and thus own it and be responsible for it, thus committing to maintaining it throughout its lifetime

• My image's repository (where the build recipes are hosted) is public

• I agree to have the provided contacts added to the Image Maintainers mailing list in Launchpad

• This image is meant to be published to the 'ubuntu' namespace, and thus a new registry repository should be created

• I acknowledge that this image shall be monitored by the security team and that I've made the necessary modifications
  to support that

• I commit to address image issues in a timely manner and according to their severity

• I will always provide up-to-date documentation for this image

• I understand the OCI tagging convention

• I understand the image's stability commitments

• I will test my image before proposing new build and releases

Security enablement

This has already been discussed and approved, but here's the upstream project of the ROCK: https://github.com/grafana/loki

Primary contact

[email protected]

Backup contact

No response

[lucabello]

Description: Loki is a horizontally scalable, highly available, multi-tenant log aggregation system inspired by Prometheus. It is designed to be very cost effective and easy to operate. It does not index the contents of the logs, but rather a set of labels for each log stream. Read more on the official website.

[cjdcordeiro]

Thanks Luca.

This image already exists - https://hub.docker.com/r/ubuntu/loki - so it should already be ok from @metorino 's side.

The only thing I'll ask is: since the existing image is not a ROCK, please make sure to adjust your documentation accordingly in #48. This is mainly because the current Usage instructions are not compatible with ROCKs, so the docs should reflect this information.