Events History

The event API allows to retrieve some special events related to cluster handling hyperindexes.

Retrieve events count

GET /api/monitor/get/event/count/:start/:end

This endpoint retrieve the number of events starting between :start and :end timestamps.

Example:

curl http://myindeximacluster:8082/api/monitor/get/event/count/1667075793000/1667075937000 \
  -H "Authorization: $ACCESS_TOKEN" \
  -H "Monitor-Target-Host: indexima-core-1" \
  -H "Monitor-Target-Port: 9999" \
  --compressed -s | jq

Retrieve events listing

GET /api/monitor/get/event/desc/:start/:end/:limit

GET /api/monitor/get/event/asc/:start/:end/:limit

This endpoint retrieve all events starting between :start and :end timestamps.
Events will be ordered ascending with /get/event/asc or descending with /get/event/desc .
The timestamps for :start and :end are unix timestamps in milliseconds.
The parameter :limit is the maximum number of events to retrieve.

Example:

curl http://myindeximacluster:8082/api/monitor/get/event/desc/1667075793000/1667075937000/2 \
  -H "Authorization: $ACCESS_TOKEN" \
  -H "Monitor-Target-Host: indexima-core-1" \
  -H "Monitor-Target-Port: 9999" \
  --compressed -s | jq

Reply JSON Format:

Name	Type	Description
(reqs | runnings).type	String	Name of the event
(reqs | runnings).date	Timestamp	Unix timestamp for the start of the event
(reqs | runnings).duration	Integer	Time it took for the event to execute, if available
(reqs | runnings).comment	String	A comment associated with the event, if available
last	Long	The timestamp of the current listing

Event list:

Name	Comment in the event	Description
CLUSTER_START	None	Cluster starts, tables aren't loaded yet
CLUSTER_STOP	None	Cluster stops, thereby receiving a stop command
NODE_DOWN	Number of the node	A specific node is unreachable
CLUSTER_INIT	None	Cluster is reinitializing
MEMORY_LOW	None	Cluster runs out of memory and tries to unload indexes
TABLE_LOADED	Name of the table	A specific table is loaded and available
HYPER_INDEX_LOADED	Name of the index	A HyperIndex is loaded and available
HYPER_INDEX_UNLOADED	Name of the index	A HyperIndex is unloaded because it is lacking memory
SAVE_METADATA	Number of tables that has been upgraded	Cluster is saving metadata
PRELOAD_FINISHED	Number of indexes loaded	Load of frequently used tables is finished (during the start of the cluster)