eggs/monitoring/loki
Charles 756816a240
image updates (#2844)
* image updates

replaced basic debian with installers
Changed pterodactyl images to use parker images

* replace alpine images

update alpine* to use installer:alpine
Remove extra space <3

* Remove use of all quay.io images

* Update all eggs to PTDL_v2

* Add back features to generic dart

* move away from bullseye or buster

* Fix Muse install

---------

Co-authored-by: Quinten <67589015+QuintenQVD0@users.noreply.github.com>
2024-04-07 15:03:34 +02:00
..
egg-loki.json image updates (#2844) 2024-04-07 15:03:34 +02:00
README.md feaT: Add Loki egg (#1606) 2022-07-04 00:51:38 +03:00

Loki

From the Loki GitHub repository

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.

Working with Loki

To get logs "into" Loki you need a scrape agent, such as official Promtail or a library for your app that can push logs through HTTP endpoint (gRPC endpoint is disabled in Docker enviroment by default)

Resource consumption

As this egg sets up Loki in single node mode, it can consume a lot of disk space really fast. It is possible to setup different kind of storages for different parts of Loki files. For further information refer to official Loki documentation.

To get started, you can go with a minimum of 3GB RAM and >=2.5GB disk space.

Keep in mind that those numbers can grow pretty quick!

Server Ports

Ports required to run the server in a table format.

Port default
Loki server 3100