Appendix C. VictoriaLogs fields and sources
The logs datasource holds file logs and journald entries from every node. Fields observed in the last six hours are listed below; the audit and event fields are structured (JSON) log lines from pan-api and the realm event system.
| Field group | Fields |
|---|---|
| Stream identity | _time, _msg, _stream, _stream_id, job, host_id, node_name, dataserial, hwserial, shelfserial, version, platform, role |
| File logs | filename (for example /pan/var/log/modules/hagent.log, /pan/var/log/net_mon.log, /pan/var/log/cpu_mon.log, /pan/var/log/mem_mon.log, /pan/var/log/core_manager.log, /pan/var/log/sysstat.log, /var/log/pan_config.log, /var/log/panapi-audit.log), level, severity, logger |
| journald | unit (pan_monitor2.service, pan_network_setup.service, vdura-log-agent.service, vdura-metrics-agent.service, vdura-service-registry.service, zfs-zed.service, sshd.service …), priority, syslog_id, transport |
| API audit (panapi-audit.log) | client_ip, method, request_id, result, status_code, action, resource, target_id, tenant_id, user_id |
| Realm events | event_id, event_code, event_name, event_category, event_delivered, component_type, blade_serial, hw_serial, node_data_serial, node_ip_address, shelf_serial, slot_id |