pub struct Log {
pub date: DateTime<Utc>,
pub domain_id: i64,
pub domain_type: String,
pub id: i64,
pub level: i64,
pub message: String,
pub person: Option<DomainObjectPerson>,
pub person_id: i64,
pub person_name: String,
pub simulate_person: Option<DomainObjectPerson>,
pub simulate_person_id: Option<i64>,
pub extra: Map<String, Value>,
}Expand description
ChurchTools writes log messages for many events and changes. This can be an update for a person or the deletion of an event. You can use the log to debug your system and follow error messages. This is a versitile tool.
Fields§
§date: DateTime<Utc>Timestamp of log
domain_id: i64Analog to the domain type, the ID is the explicit resource.
domain_type: StringThe domain type tells us, where in ChurchTools the action was performed.
id: i64§level: i64The log level indicates the importance. 1 = Warning, 2 = Notice, 3 = Info.
message: String§person: Option<DomainObjectPerson>§person_id: i64If the person ID is -1, that means, no person but the system itself has logged that message.
person_name: StringThe name of the person, who caused the log message. This is stored in the log, because the person could be deleted later. So we have the name in the log, even if the person is deleted.
simulate_person: Option<DomainObjectPerson>§simulate_person_id: Option<i64>If a person is simulated by an administrator, we log the personId as well. This makes it possible to see if a person did the action or an admin, who simulated that person.
extra: Map<String, Value>Fields not described by the spec, e.g. instance-specific DB fields.