ArangoDB V 2.4.5: Introducing Slow Query Tracking

This version is deprecated. Download the new version of ArangoDB

ArangoDB 2.4.5 is ready to download. The latest release of the 2.4 branch comes with some minor bugfixes and a new feature:

Tracking of AQL queries

We have added current and slow query tracking and also killing of long running AQL queries.

This change enables retrieving the list of currently running AQL queries inside the selected database. AQL queries with an execution time beyond a certain threshold can be moved to a slow query facility and retrieved from there:

Queries can also be killed by specifying the query id or with just one click in the web interface:

This change adds the following HTTP REST APIs:

GET /_api/query/current    // for retrieving the list of currently running queries
GET /_api/query/slow       // for retrieving the list of slow queries
DELETE /_api/query/slow    // for clearing the list of slow queries
GET /_api/query/properties // for retrieving the properties for query tracking
PUT /_api/query/properties // for adjusting the properties for query tracking
DELETE /_api/query/<id>    // for killing an AQL query

The following JavaScript APIs have been added:

• require(“org/arangodb/aql/queries”).current();
• require(“org/arangodb/aql/queries”).slow();
• require(“org/arangodb/aql/queries”).clearSlow();
• require(“org/arangodb/aql/queries”).properties();
• require(“org/arangodb/aql/queries”).kill();

Note: This feature will also be available with the version 2.5.1 later this week!

Other changes and fixes in 2.4.5:

• added elapsed time to HTTP request logging output (--log.requests-file)
• fixed issue #1265: arangod crashed with SIGSEGV
• fixed issue #1241: Wildcards in examples
• fixed comment parsing in Foxx controllers