Logging
Kismet uses a centralized logging architecture which manages enabling and tracking the status of logs. The logging system integrates with the streaming sytem for long-running log files.
Log drivers
Log drivers handle a specific type of logfile.
-
URL
/logging/drivers.json
/logging/drivers.ekjson
/logging/drivers.itjson
-
Methods
GET
-
Role
readonly
-
Result
Array of supported log types
Active logs
Not all drivers are activated depending on the Kismet config optins.
-
URL
/logging/active.json
/logging/active.ekjson
/logging/active.itjson
-
Methods
GET
-
Role
readonly
-
Result
Array of activated logs.
Enabling logs
Logs can be enabled run-time.
-
URL
/logging/by-class/[LOGCLASS]/start.cmd
-
Methods
GET
POST
-
Role
admin
-
URL parameters
Key Description [LOGCLASS] Kismet log class to enable -
POST parameters
A command dictionary containing:
Key Description title Alternate log title, overriding the kismet_logging.conf
config forlog_title=
-
Results
HTTP 200
and log object for newly created log on successHTTP error on failure
Stopping logs
Logs can be stopped run-time. The log must be open and running to be stopped.
-
URL
/logging/by-uuid/[LOGUUID]/stop.cmd
-
Methods
GET
-
Role
admin
-
URL parameters
Key Description [LOGUUID] Kismet log UUID to stop -
Results
HTTP 200
on successHTTP error on failure