Page MenuHomePhorge
Files F117758540

No OneTemporary
Actions

Authored By
Unknown
Size
3 KB
Referenced Files
None
Subscribers
None

View Options

diff --git a/docs/docs/home/what-is-kolab.md b/docs/docs/home/what-is-kolab.md
index 46523d8..79f576a 100644
--- a/docs/docs/home/what-is-kolab.md
+++ b/docs/docs/home/what-is-kolab.md
@@ -1,27 +1,27 @@
# What is Kolab?
[Kolab](https://kolab.org) is a [FOSS](https://en.wikipedia.org/wiki/Free_and_open-source_software) communication & collaboration solution that can be completely self-hosted,
and allows you to maintain control over your most sensitive data.
Kolab integrates various components to provide you with a wide range of features:
* Being able to send & receive email including:
* spam filtering
* virus scanning
* Support for important protocols that ensure secure email delivery (DKIM/DMARC/SPF)
* A variety of access protocols:
* IMAP/SMTP
* ActiveSync
* CalDAV/CardDAV
* A webmail client that includes advanced calendaring/tasks/addressbook
* A webrtc based video chat solution
* File storage
* Collaborative editing of documents
In short, it provides everything that a company/family/... needs to work and communicate together, while maintaining full control over all data.
-Further:
+Other features:
* Kolab makes extensive use of open protocols and standards, where available, to avoid vendor lock-in, and improve interoperability
* Kolab is built exclusively on open source software, and can be built from source.
* The Kolab Web-Clients do not load data from any external sources and are fully self-reliant, which makes them suitable to be used in air-gapped environments and avoids any tracking.
diff --git a/docs/docs/overview/logging.md b/docs/docs/overview/logging.md
index d42ffe0..d3f46a4 100644
--- a/docs/docs/overview/logging.md
+++ b/docs/docs/overview/logging.md
@@ -1,23 +1,46 @@
# Observability
## Logging
Kolab is distributed with a logging pipeline that works like this:
* Applications running in containers log to stdout/stderr, which is captured by Kubernetes.
* The vector.dev daemonset picks up the Kubernetes logs and generates a stream of structured log events from each log line.
* vector.dev further processes each event to extract structured log fields from the log lines in the various formats (apache, logfmt, ...)
* The resulting log events are forwarded to victorialogs for storage and retrieval
-### Kubernetes logging and vector.dev
+### Kubernetes logging and vector.dev in a k3s setup
+
+K3s stores pod logs in files like this:
+
+```
+/var/log/pods/kolab_scheduler-29320110-5z858_77c55590-3932-4dc5-a77e-7aef4d32af73/scheduler/0.log
+```
+
+These files are detected and ingested by vector.dev (see vector container output).
+
+With a lot of log output the log-files will rotate quickly (every couple of seconds) and it is important,
+that vector.dev will notice new files quickly enough, otherwise parts of the log output may be missing from
+the log stream. vector.dev is configured with a relatively low `glob_minimum_cooldown_ms` for this reason.
### Victorialogs
+Victorialogs provides a simple webinterface at `/select/vmui/`, which can be used to query for logs.
+
+A simple query might look like this:
+
+```
+{pod_name=~"postfix.*"} disconnect
+```
+This will query for logs from all postfix pods, and filter for the string "disconnect".
+
+Alternatively it is possible to query for logs via the [HTTP API](https://docs.victoriametrics.com/victorialogs/querying/).
+
## Metrics
Kolab is distributed with a prometheus instance that scrapes internal metrics and has various alerts pre-configured.
## Alerting
Kolab can be configured to provide an internal [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) instance, or use an external instance,
to receive alerts generated by both Prometheus and Victorialogs.

File Metadata

Mime Type
text/x-diff
Expires
Sat, Apr 4, 9:49 AM (3 w, 6 d ago)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
18792078
Default Alt Text
(3 KB)

Event Timeline