Skip to content

Commit ac2cca6

Browse files
authored
Merge pull request #681 from ethersphere/logging-update-1-7-25
add notices to logging section
2 parents 4e0877a + d2a0b35 commit ac2cca6

File tree

1 file changed

+9
-4
lines changed

1 file changed

+9
-4
lines changed

docs/bee/working-with-bee/logs-and-files.md

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,19 @@
11

22
# Logging in Bee
33

4-
This section introduces logging in Bee, detailing log locations, exporting logs, setting the general verbosity level, and setting fine-grained verbosity for individual loggers.
4+
This section provides an overview of logging in Bee, including log locations, exporting logs, managing verbosity levels, and using fine-grained control for specific loggers.
55

6-
## Log Locations
6+
:::info
7+
Bee uses a structured logging format compatible with popular tools such as [Grafana](https://grafana.com/) and [Elasticsearch](https://www.elastic.co/elasticsearch). Structured logging helps streamline log analysis and management by organizing data into machine-readable formats which enable easy integration with monitoring and debugging tools.
8+
:::
79

8-
:::warning
9-
Bee logs by default can be quite verbose, and over time may occupy disk space in the gigabytes range. You may wish to practice log rotation to prevent excessive disk utilization.
10+
:::warning
11+
Bee logs can be verbose by default, potentially consuming significant disk space over time. Consider implementing [log rotation](https://en.wikipedia.org/wiki/Log_rotation) to prevent excessive disk utilization.
1012
:::
1113

14+
15+
## Log Locations
16+
1217
### **Linux (Package Manager Installation)**
1318
When installed via a package manager (e.g., `APT`, `RPM`), Bee runs as a **systemd service**, and logs are managed by the system journal, **journalctl**.
1419

0 commit comments

Comments
 (0)