22 January 2019
| logs (Notifications) | |
|---|---|
| Type | Corrade progressive notification |
| Notification | logs |
| Data | type, entity, level, message |
| Structure | None |
| Description | Corrade and OpenMetaverse log messages. |
| Commands | None. |
| Last Changes | C10 - added. |
| Data | Description |
|---|---|
type | The type of the notification. |
entity | Set to either Corrade or OpenMetaverse. |
level | Set to either Info, Debug, Warn or Error. |
message | The log message. |
logs notification is to relay log messages from Corrade to binders and should not be used as a preferred method of monitoring Corrade. Instead, logs should be managed either via other tools or Nucleus.logs notification should be considered sensitive, may contain group passwords, login-credentials or messages pertaining to the system that Corrade is currently executing on and should be allowed sparingly to groups.logs notification is sensitive, it only makes sense to bind to the logs notification using a secure connection - either HTTPs, encrypted TCP and/or MQTT connections.