Git-Mirrors/constellation
1
0
Fork 0
mirror of https://github.com/edgelesssys/constellation.git synced 2025-09-18 12:04:41 -04:00
Code Issues Projects Releases Packages Wiki Activity

docs: remove broken links and publish removal of cloud logging

Browse source
This commit is contained in:
Thomas Tendyck 2024-02-22 21:58:34 +01:00 • committed by Thomas Tendyck
parent 2a61861a1c
commit 31baba2d4b
5 changed files with 9 additions and 52 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/versioned_docs/version-2.15/architecture/observability.md
View file

@ -33,11 +33,7 @@ The payload is an actual message emitted from your system along with a metadata
### System logs
Constellation uses cloud logging for events occurring during the early stages of a node's boot process.
These logs include [Bootstrapper](./microservices.md#bootstrapper) events and [state disk UUIDs](../architecture/images.md#state-disk).
You can access the cloud logging [directly via the cloud provider endpoints](../workflows/troubleshooting.md#cloud-logging).
More detailed system-level logs are accessible via `/var/log` and [journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) on the nodes directly.
Detailed system-level logs are accessible via `/var/log` and [journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) on the nodes directly.
They can be collected from there, for example, via [Filebeat and Logstash](https://www.elastic.co/guide/en/beats/filebeat/current/logstash-output.html), which are tools of the [Elastic Stack](https://www.elastic.co/de/elastic-stack/).
In case of an error during the initialization, the CLI automatically collects the [Bootstrapper](./microservices.md#bootstrapper) logs and returns these as a file for [troubleshooting](../workflows/troubleshooting.md). Here is an example of such an event: