LOGGER table stores only integers, any textual description is automatically added into lookup table LOGGER_LABELS.
Label of any event is added at first use.
- Username: If you have application with authorisation enabled, logger class stores ID of currently logged user
- Logger: Specified in logger constructor. You can have more than one logger in application, with different configurations.
- Event and ID: Any action in our application is identified by string (route)
"$controller/$action/$id" which means: do action $action of controller $controller with object $id.
This structure is supported by class 'app' (now in experimental stage).
However, Event (Action) label is plain text, so you can log anything here.
We use Action label in format "appname/controller/action" where appname is application name (demo) and controller is name of the visited example.
- MSG: It's possible add free text message to any event. If you add message, it is stored in table LOGGER_MESSAGES.
- Try click on these links, for adding events into log:
| Timestamp | Username | Category | Logger | Event | User Agent | ID | MSG | |
|---|---|---|---|---|---|---|---|---|
| 2026-04-23 18:39:06 | WARNING | app-monitor | demo/eventlog/warning1 | ? Mozilla like | 74.7.227.xxx | |||
| 2026-04-23 18:39:05 | NOTICE | app-monitor | demo/eventlog/eventlog | ? Mozilla like | 74.7.227.xxx | 100 | ||
| 2026-04-23 18:39:01 | NOTICE | app-monitor | demo/eventlog/eventlog | ? Mozilla like | 74.7.227.xxx | 0 | ||
| 2026-04-22 22:33:49 | NOTICE | app-monitor | demo/eventlog/eventlog | Windows Safari | 194.110.115.xxx | 0 | ||
| 2026-04-22 22:33:49 | NOTICE | app-monitor | demo/eventlog/eventlog | Android Safari | 194.110.115.xxx | 0 | ||
| 2026-04-22 22:33:48 | NOTICE | app-monitor | demo/eventlog/eventlog | ? ? | 194.110.115.xxx | 0 | ||
| 2026-04-19 14:44:48 | WARNING | app-monitor | demo/eventlog/warning1 | MacOS Chrome | 150.109.44.xxx | |||
| 2026-04-17 06:32:14 | NOTICE | app-monitor | demo/eventlog/eventlog | ? Mozilla like | 54.37.118.xxx | 0 | ||
| 2026-04-17 06:29:39 | NOTICE | app-monitor | demo/eventlog/eventlog | ? Mozilla like | 5.39.109.xxx | 100 | ||
| 2026-04-17 06:26:44 | WARNING | app-monitor | demo/eventlog/warning1 | ? Mozilla like | 5.39.1.xxx | |||
| 2026-04-16 16:41:34 | NOTICE | app-monitor | demo/eventlog/eventlog | Windows Chrome | 146.70.132.xxx | 0 | ||
| 2026-04-16 16:41:34 | NOTICE | app-monitor | demo/eventlog/eventlog | Linux Chrome | 146.70.132.xxx | 0 | ||
| 2026-04-16 16:41:33 | NOTICE | app-monitor | demo/eventlog/eventlog | Linux Chrome | 146.70.132.xxx | 0 | ||
| 2026-04-10 09:26:35 | WARNING | app-monitor | demo/eventlog/warning1 | ? Mozilla like | 178.150.14.xxx | |||
| 2026-04-10 09:26:32 | NOTICE | app-monitor | demo/eventlog/eventlog | ? Mozilla like | 178.150.14.xxx | 100 | ||
| 2026-04-10 09:26:28 | NOTICE | app-monitor | demo/eventlog/eventlog | ? Mozilla like | 178.150.14.xxx | 0 | ||
| 2026-04-09 20:58:19 | WARNING | app-monitor | demo/eventlog/warning1 | ? Mozilla like | 81.167.26.xxx | |||
| 2026-04-09 20:58:16 | NOTICE | app-monitor | demo/eventlog/eventlog | ? Mozilla like | 81.167.26.xxx | 100 | ||
| 2026-04-09 20:58:13 | NOTICE | app-monitor | demo/eventlog/eventlog | ? Mozilla like | 81.167.26.xxx | 0 | ||
| 2026-04-09 20:58:10 | WARNING | app-monitor | demo/eventlog/warning1 | ? Mozilla like | 81.167.26.xxx |
Source code: eventlog.php | eventlog.tpl