System status
System status
The status endpoint returns almost all data around the current system status, load, system health, thermal and fan sensors (if any), memory use, battery state, runtime, and more.
After 2026-10-R1 it also has the CPU load, which the kismetdb SYSTEM snapshots log with
the rest of the status:
| Field | Contents |
|---|---|
kismet.system.cpu.available | 1 when the CPU load can be read (Linux) |
kismet.system.cpu.count | Number of CPUs online |
kismet.system.cpu.total | CPU load of the system over the last second, as a percent of all the CPUs |
kismet.system.cpu.kismet | CPU load of the Kismet server process over the last second, as a percent of all the CPUs |
kismet.system.sensors.temp holds every temperature sensor, after 2026-10-R1 including all
the Linux thermal zones (system-thermal-0, system-thermal-1, and so on).
readonly/system/status.json/system/status.ekjson/system/status.prettyjsonGET
POSTPARAMETERS
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.
fields
field simplification
OPTIONALKismet can reduce the amount of information being processed and returned by an API by simplifying the fields to only return the data needed by the caller.
You can read more about the field simplification API and how to use it here.
Memory detail
The memory endpoint returns what the memory window
of the web UI shows: the process, heap, and system memory, their history, and the
memory settings in effect. It has the memory and device
fields of /system/status (kismet.system.memory.rss, kismet.system.memory.rrd,
kismet.system.devices.count, kismet.system.devices.rrd, kismet.system.num_fields,
kismet.system.num_components, kismet.system.num_http_connections, and
kismet.system.string_cache_sz), and adds:
| Field | Contents |
|---|---|
kismet.system.memory.peak_rss | The most memory Kismet has used, in kB |
kismet.system.memory.virtual | Virtual memory size, in kB |
kismet.system.memory.rss_anon | Memory in use for the heap and stacks, in kB |
kismet.system.memory.rss_file | Memory in use for the program and libraries, in kB |
kismet.system.memory.rss_shmem | Shared memory in use, in kB |
kismet.system.memory.swap | Memory swapped out, in kB |
kismet.system.memory.threads | Number of threads |
kismet.system.memory.system_total | The system’s memory, in kB |
kismet.system.memory.system_available | System memory available, in kB |
kismet.system.memory.system_used_rrd | History of system memory in use |
kismet.system.memory.heap_known | 1 when the heap values are available |
kismet.system.memory.heap_used | Heap in use, in kB |
kismet.system.memory.heap_free | Heap freed and held by the allocator for reuse, in kB |
kismet.system.memory.heap_mmap | Large allocations mapped on their own, in kB |
kismet.system.num_fields_rrd | History of the number of tracked fields |
kismet.system.memory.startup_time | When Kismet had loaded, before opening data sources (unix time); 0 until then |
kismet.system.memory.startup_rss | Memory in use once Kismet had loaded, in kB |
kismet.system.memory.startup_rss_anon | Heap and stacks once Kismet had loaded, in kB |
kismet.system.memory.startup_heap_used | Heap in use once Kismet had loaded, in kB; 0 when unknown |
kismet.system.memory.startup_heap_mmap | Large allocations mapped on their own once Kismet had loaded, in kB |
kismet.system.memory.startup_fields | Tracked fields once Kismet had loaded |
kismet.system.memory.datasources | Number of data sources |
kismet.system.memory.datasource_estimate | Estimated heap each data source holds in Kismet, in kB, not counting its devices or its capture helper process |
kismet.system.memory.packet_pool | Freed packets kept for reuse |
kismet.system.memory.packet_pool_estimate | Estimated heap held by those packets, in kB |
kismet.system.memory.dedupe_packets | Recent packets kept to recognize duplicates (up to 1,024 per packet thread, from the last second) |
kismet.system.memory.dedupe_estimate | Estimated heap held by those packets, in kB |
kismet.system.memory.settings | The settings in effect which change memory use, by their config names: the device tracker settings (tracker_device_timeout, tracker_max_devices, tracker_device_presize, and the rest of kismet_memory.conf), alertbacklog, packet_backlog_warning, packet_backlog_limit, manuf_lookup, the pcapng buffer and ring sizes, the 802.11 settings which keep data (dot11_keep_eapol, dot11_keep_ietags, dot11_ap_only_survey, and others), kismet_packet_threads, and ulimit_mbytes (the data size limit, 0 when unlimited) |
The process and system values are read from /proc and are only present on Linux. The heap
values need glibc 2.33 or newer, and are read at most every 5 seconds. /system/status and
the kismetdb SYSTEM snapshots are unchanged.
The startup values are recorded once, after plugins and device rules have loaded and before the data sources open, so the memory a running Kismet has added since (devices, sources, packets) can be told apart from what it needs to run at all.
readonly/system/memory.json/system/memory.ekjson/system/memory.prettyjsonGET
POSTPARAMETERS
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.
fields
field simplification
OPTIONALKismet can reduce the amount of information being processed and returned by an API by simplifying the fields to only return the data needed by the caller.
You can read more about the field simplification API and how to use it here.
Temperatures
The thermal endpoint returns what the thermal window of the web UI shows: every temperature sensor Kismet has read since it started, and its history.
| Field | Contents |
|---|---|
kismet.system.thermal.history | 1 when history is kept (system_thermal_history) |
kismet.system.thermal.sensors | The sensors, by name |
Each sensor has:
| Field | Contents |
|---|---|
kismet.system.thermal.sensor.name | The sensor’s name, as in kismet.system.sensors.temp of /system/status |
kismet.system.thermal.sensor.label | What the sensor measures, such as the lm-sensors label and chip, or the thermal zone type |
kismet.system.thermal.sensor.temp | The last temperature, in degrees C |
kismet.system.thermal.sensor.last_time | When the sensor was last read; a sensor no longer read keeps its last values |
kismet.system.thermal.sensor.rrd | History of the temperature, in degrees C, when history is kept. Seconds, minutes, and hours with no reading hold the RRD’s kismet.common.rrd.blank_val |
The current temperatures are also sent every second as the THERMAL eventbus
topic, with the field kismet.system.sensors.temp.
readonly/system/thermal.json/system/thermal.ekjson/system/thermal.prettyjsonGET
POSTPARAMETERS
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.
fields
field simplification
OPTIONALKismet can reduce the amount of information being processed and returned by an API by simplifying the fields to only return the data needed by the caller.
You can read more about the field simplification API and how to use it here.
CPU load
The CPU endpoint returns the CPU load fields of /system/status (kismet.system.cpu.available,
kismet.system.cpu.count, kismet.system.cpu.total, and kismet.system.cpu.kismet), and adds
their history:
| Field | Contents |
|---|---|
kismet.system.cpu.total_rrd | History of the CPU load of the system, as a percent of all the CPUs |
kismet.system.cpu.kismet_rrd | History of the CPU load of the Kismet server process, as a percent of all the CPUs |
The load is read from /proc and is only available on Linux. The load of the capture tools,
which run as their own processes, isn’t counted in Kismet’s. The current load is also sent
every second in the STATISTICS eventbus topic.
readonly/system/cpu.json/system/cpu.ekjson/system/cpu.prettyjsonGET
POSTPARAMETERS
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.
fields
field simplification
OPTIONALKismet can reduce the amount of information being processed and returned by an API by simplifying the fields to only return the data needed by the caller.
You can read more about the field simplification API and how to use it here.
Timestamp
readonly/system/timestamp.json/system/timestamp.ekjson/system/timestamp.prettyjsonGETTracked fields
To aid in development, Kismet maintains a list of all known field names, data types, and descriptions.
This endpoint returns a human-readable HTML page of all fields.
readonly/system/tracked_fields.htmlGETPacket statistics
Kismet exposes the packet processing statistics as RRD (round robin database) collections for incoming packet rate, packet proessing rates, data size, and more.
The RRD format encodes long-running data as collections of decreasing accuracy, reporting the past 60 seconds, past hour as 60 second averages, and past day as 1 hour averages.
readonly/packetchain/packet_stats.json/packetchain/packet_stats.ekjson/packetchain/packet_stats.prettyjsonGET
POSTPARAMETERS
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.
fields
field simplification
OPTIONALKismet can reduce the amount of information being processed and returned by an API by simplifying the fields to only return the data needed by the caller.
You can read more about the field simplification API and how to use it here.
Map tile server
The tile server the web UI map uses for browsers which haven’t set their own, from the map background options. None of it is secret, so no login is needed.
| Key | Content |
|---|---|
url | httpd_map_tile_url, or empty for the UI’s default (OpenStreetMap) |
attribution | httpd_map_tile_attribution, or empty |
tiles | httpd_map_tiles: ask or deny |
The UI always asks the user before loading tiles from a server they haven’t agreed to.
none/ui/map_tiles.jsonGETDynamic Javascript import
Kismet creates a dynamically generated javascript file for the UI to load the core system and JS plugin modules into the global JS namespace.
This endpoint is meant to be used by a web-based UI and included as a script import, such as:
<script src="dynamic.js"></script>
readonly/dynamic.jsGETUser status
none/system/user_status.json/system/user_status.ekjson/system/user_status.prettyjsonGET
POSTkismet.system.user, the system user Kismet is running as.Incoming packet rate
RRD (round robin database) record of every packet received by Kismet, including packets which are later dropped.
This is one of the RRDs included in the packet statistics; see the RRD documentation for the RRD format.
readonly/packetchain/packet_rate.json/packetchain/packet_rate.ekjson/packetchain/packet_rate.prettyjsonGET
POSTPARAMETERS
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.
fields
field simplification
OPTIONALKismet can reduce the amount of information being processed and returned by an API by simplifying the fields to only return the data needed by the caller.
You can read more about the field simplification API and how to use it here.
Incoming packet peak rate
RRD (round robin database) record of every packet received by Kismet, including packets which are later dropped.
This is one of the RRDs included in the packet statistics; see the RRD documentation for the RRD format.
readonly/packetchain/packet_peak.json/packetchain/packet_peak.ekjson/packetchain/packet_peak.prettyjsonGET
POSTPARAMETERS
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.
fields
field simplification
OPTIONALKismet can reduce the amount of information being processed and returned by an API by simplifying the fields to only return the data needed by the caller.
You can read more about the field simplification API and how to use it here.
Processed packet rate
RRD (round robin database) record of packets which have been fully processed.
This is one of the RRDs included in the packet statistics; see the RRD documentation for the RRD format.
readonly/packetchain/packet_processed.json/packetchain/packet_processed.ekjson/packetchain/packet_processed.prettyjsonGET
POSTPARAMETERS
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.
fields
field simplification
OPTIONALKismet can reduce the amount of information being processed and returned by an API by simplifying the fields to only return the data needed by the caller.
You can read more about the field simplification API and how to use it here.
Error packet rate
RRD (round robin database) record of processed packets marked as errors, such as corrupt or undecodable frames. Packets with an invalid checksum are not counted as errors.
This is one of the RRDs included in the packet statistics; see the RRD documentation for the RRD format.
readonly/packetchain/packet_error.json/packetchain/packet_error.ekjson/packetchain/packet_error.prettyjsonGET
POSTPARAMETERS
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.
fields
field simplification
OPTIONALKismet can reduce the amount of information being processed and returned by an API by simplifying the fields to only return the data needed by the caller.
You can read more about the field simplification API and how to use it here.
Duplicate packet rate
RRD (round robin database) record of processed packets identified as duplicates, such as the same packet received by multiple datasources.
This is one of the RRDs included in the packet statistics; see the RRD documentation for the RRD format.
readonly/packetchain/packet_dupe.json/packetchain/packet_dupe.ekjson/packetchain/packet_dupe.prettyjsonGET
POSTPARAMETERS
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.
fields
field simplification
OPTIONALKismet can reduce the amount of information being processed and returned by an API by simplifying the fields to only return the data needed by the caller.
You can read more about the field simplification API and how to use it here.
Dropped packet rate
RRD (round robin database) record of packets dropped because the packet processing queue was full. The queue size is set by packet_backlog_limit in kismet_memory.conf.
This is one of the RRDs included in the packet statistics; see the RRD documentation for the RRD format.
readonly/packetchain/packet_drop.json/packetchain/packet_drop.ekjson/packetchain/packet_drop.prettyjsonGET
POSTPARAMETERS
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.
fields
field simplification
OPTIONALKismet can reduce the amount of information being processed and returned by an API by simplifying the fields to only return the data needed by the caller.
You can read more about the field simplification API and how to use it here.