Logging

Fetch a list of all available log drivers.

Each logging driver handles a log output format.

List enabled and active logs

After 2026-10-R1, each log has kismet.logfile.rotate_overdue_since: the time (unix seconds) the kismetdb log’s next file was due but hasn’t been started yet, or 0 when it isn’t late.

Open a new log; if the same type of log is closed and opened multiple times in one session, it will have multipe log instances (such as Kismet-foo-2022-10-03-1.pcap, kismet-foo-2022-10-03-2.pcap )

After 2026-10-R1, an optional title, sent as POST JSON, names only the log being opened; the session title, and the other logs, are unchanged. The title is 1 to 64 characters of A-Z, a-z, 0-9, ., _, and -, not starting with .; any other title is refused, and no log is opened.

This endpoint takes additional parameters by using a `POST` request and supplying a JSON document or json form variable.

You can find more information about API parameters here.

After 2026-10-R1, closes the current file of a kismetdb or pcapng log and continues the log in a new file, the same as when the log reaches kis_log_max_mb / kis_log_max_seconds or pcapng_log_max_mb / pcapng_log_max_seconds. The new file starts shortly after the request returns, and no packets are lost.

The log template needs %i, so the new file gets the next sequence number.

When the old file is closed and complete, a LOG_FINISHED event is published on the eventbus with the reason api.