Server Statistics - Kozea/Radicale GitHub Wiki

Server Statistics

Server Statistics using logwatch

Since 3.3.3 there is a logwatch example configuration bundled, can be found here: https://github.com/Kozea/Radicale/tree/master/contrib/logwatch

Server Statistics using logwatch on Fedora/Enterprise Linux

A sub-package named "radicale3-logwatch" is available and works out-of-the-box after installation

Server Statistics using logwatch in a manual way

Preconditions on a Linux system:

  • Perl is installed
  • Logwatch service file is available
  • Radicale logfile to analyze is available

Examples:

## service file is stored in default logwatch directory
# source: logfile
cat radicale.log | LOGWATCH_DETAIL_LEVEL=10 perl /usr/share/logwatch/scripts/services/radicale
# source: journald since last boot
journalctl -b 0 -u radicale | LOGWATCH_DETAIL_LEVEL=10 perl /usr/share/logwatch/scripts/services/radicale

## service file used from Radicale repository
# source: logfile
cat radicale.log | LOGWATCH_DETAIL_LEVEL=10 perl contrib/logwatch/radicale
# source: journald since last boot
journalctl -b 0 -u radicale | LOGWATCH_DETAIL_LEVEL=10 perl contrib/logwatch/radicale

Example output as of 3.5.11

Detail = Low

**Loglevel counters**
Loglevel           |     cnt |     ratio |
------------------------------------------
INFO               |   38506 |   99.455% |
WARNING            |     211 |    0.545% |
------------------------------------------
                   |   38717 |  100.000% |

**Request counters (D=<depth>)**
Request      |     cnt |     ratio |
------------------------------------
DELETE       |       4 |    0.031% |
GET          |     656 |    5.030% |
OPTIONS      |     111 |    0.851% |
PROPFIND:D=0 |    5707 |   43.759% |
PROPFIND:D=1 |     876 |    6.717% |
PUT          |     490 |    3.757% |
REPORT       |      74 |    0.567% |
REPORT:D=0   |       8 |    0.061% |
REPORT:D=1   |    5116 |   39.227% |
------------------------------------
                   |   13042 |  100.000% |

**Response result counters ((D=<depth> R=<result>)**
Response           |     cnt |     ratio |
------------------------------------------
DELETE:R=200       |       4 |    0.031% |
GET:R=200          |     656 |    5.113% |
OPTIONS:R=200      |     111 |    0.865% |
PROPFIND:D=0:R=207 |    5707 |   44.478% |
PROPFIND:D=1:R=207 |     876 |    6.827% |
PUT:R=201          |      28 |    0.218% |
PUT:R=204          |      40 |    0.312% |
PUT:R=412          |     211 |    1.644% |
REPORT:D=0:R=207   |       8 |    0.062% |
REPORT:D=1:R=207   |    5116 |   39.872% |
REPORT:R=207       |      74 |    0.577% |
------------------------------------------
                   |   12831 |  100.000% |

**Other Events**
Profiling data per request PROPFIND: 563 Time(s)
Profiling data per request REPORT: 6 Time(s)
Radicale server started: 2 Time(s)
Radicale server stopped: 2 Time(s)
Successful login: 12188 Time(s)

**Unmatched Entries**
Starting Radicale CalDAV and CardDAV server...: 1 Time(s)
Started Radicale CalDAV and CardDAV server.: 1 Time(s)
Started Radicale CalDAV and CardDAV server.: 1 Time(s)
Starting Radicale CalDAV and CardDAV server...: 1 Time(s)
Stopped Radicale CalDAV and CardDAV server.: 1 Time(s)
radicale.service: Consumed 1h 8min 15.324s CPU time, 149.8M memory peak.: 1 Time(s)
radicale.service: Deactivated successfully.: 1 Time(s)

Other detail levels

Detail level can be tweaked by adjusting configuration file /etc/logwatch/conf/services/radicale.conf, e.g.

# LOGWATCH_DETAIL_LEVEL=5
Detail = Medium

or

# LOGWATCH_DETAIL_LEVEL=10
Detail = High

Higher detail levels are supported, but should only be used for manual runs (can create long reports).

⚠️ **GitHub.com Fallback** ⚠️