curl http://localhost:9042/api/config
curl http://localhost:9042/api/config/reload
(Also supports PUT. You can also send a SIGHUP signal to the process)
curl 'http://localhost:9042/api/config/reload?refresh=1'
curl 'http://localhost:9042/api/config/reload?spawnpoints=all'
(refresh=1 is implied and not required)
curl http://localhost:9042/api/nests
curl http://localhost:9042/api/nests/:nest_id
curl http://localhost:9042/api/nests/_/stats
curl http://localhost:9042/api/nests/_/:nest_id
curl http://localhost:9042/debug/logging/on
curl http://localhost:9042/debug/logging/off
Untested:
curl -X PUT http://localhost:9042/api/stats/purge/all
This ditches all stats history including the current time period. This starts the stats with a clean slate, but like startup.
curl -X PUT http://localhost:9042/api/stats/purge/oldest -d '{ "duration_minutes": xx }'
Purges the specified duration of the stats starting from the oldest. This will never remove the current unfinished time period. This can be used to nuke everything but the current time period by specifying a very high number of minutes.
curl -X PUT http://localhost:9042/api/stats/purge/newest -d '{ "duration_minutes": xx, "include_current": false }'
Purges the specified amount of minutes of stats starting from the newest. 'include_current' specifies whether it should start with the current time period that is not done, or if it should start at the last period.
curl -X PUT http://localhost:9042/api/stats/purge/keep -d '{ "duration_minutes": xx }'
This is another way to purge oldest stats. But with this one, you specify the duration to keep, not the duration to purge.
curl http://localhost:9042/status