ArangoDB v2.8 reached End of Life (EOL) and is no longer supported.

This documentation is outdated. Please see the most recent version here: Try latest

HTTP Interface for Administration and Monitoring

This is an introduction to ArangoDB’s HTTP interface for administration and monitoring of the server.

Read global log from the server

returns the log files

GET /_admin/log

Query Parameters

  • upto (optional): Returns all log entries up to log level upto. Note that upto must be:
  • fatal or 0
  • error or 1
  • warning or 2
  • info or 3
  • debug or 4 The default value is info.
    • level (optional): Returns all log entries of log level level. Note that the query parameters upto and level are mutually exclusive.
    • start (optional): Returns all log entries such that their log entry identifier (lid value) is greater or equal to start.
    • size (optional): Restricts the result to at most size log entries.
    • offset (optional): Starts to return log entries skipping the first offset log entries. offset and size can be used for pagination.
    • search (optional): Only return the log entries containing the text specified in search.
    • sort (optional): Sort the log entries either ascending (if sort is asc) or descending (if sort is desc) according to their lid values. Note that the lid imposes a chronological order. The default value is asc.
      Returns fatal, error, warning or info log messages from the server’s global log. The result is a JSON object with the following attributes:
  • lid: a list of log entry identifiers. Each log message is uniquely identified by its @LIT{lid} and the identifiers are in ascending order.
  • level: a list of the log-levels for all log entries.
  • timestamp: a list of the timestamps as seconds since 1970-01-01 for all log entries.
  • text a list of the texts of all log entries
  • totalAmount: the total amount of log entries before pagination.

    Return codes

    • 400: is returned if invalid values are specified for upto or level.

    • 403: is returned if the log is requested for any database other than _system.

    • 500: is returned if the server cannot generate the result due to an out-of-memory error.

Reloads the routing information

Reload the routing table.

POST /_admin/routing/reload


Reloads the routing information from the collection routing.

Return codes

  • 200: Routing information was reloaded successfully.

Read the statistics

return the statistics information

GET /_admin/statistics


Returns the statistics information. The returned object contains the statistics figures grouped together according to the description returned by _admin/statistics-description. For instance, to access a figure userTime from the group system, you first select the sub-object describing the group stored in system and in that sub-object the value for userTime is stored in the attribute of the same name.
In case of a distribution, the returned object contains the total count in count and the distribution list in counts. The sum (or total) of the individual values is returned in sum.

Return codes

  • 200: Statistics were returned successfully.

Examples

shell> curl --dump - http://localhost:8529/_admin/statistics

HTTP/1.1 200 OK
content-type: application/json; charset=utf-8

show response body

Statistics description

fetch descriptive info of statistics

GET /_admin/statistics-description


Returns a description of the statistics returned by /_admin/statistics. The returned objects contains an array of statistics groups in the attribute groups and an array of statistics figures in the attribute figures.
A statistics group is described by

  • group: The identifier of the group.
  • name: The name of the group.
  • description: A description of the group.
    A statistics figure is described by
  • group: The identifier of the group to which this figure belongs.
  • identifier: The identifier of the figure. It is unique within the group.
  • name: The name of the figure.
  • description: A description of the figure.
  • type: Either current, accumulated, or distribution.
  • cuts: The distribution vector.
  • units: Units in which the figure is measured.

    Return codes

    • 200: Description was returned successfully.

Examples

shell> curl --dump - http://localhost:8529/_admin/statistics-description

HTTP/1.1 200 OK
content-type: application/json; charset=utf-8

show response body

Return role of a server in a cluster

Get to know whether this server is a Coordinator or DB-Server

GET /_admin/server/role


Returns the role of a server in a cluster. The role is returned in the role attribute of the result. Possible return values for role are:

  • COORDINATOR: the server is a coordinator in a cluster
  • PRIMARY: the server is a primary database server in a cluster
  • SECONDARY: the server is a secondary database server in a cluster
  • UNDEFINED: in a cluster, UNDEFINED is returned if the server role cannot be determined. On a single server, UNDEFINED is the only possible return value.

    Return codes

    • 200: Is returned in all cases.

Queries statistics of DBserver

allows to query the statistics of a DBserver in the cluster

GET /_admin/clusterStatistics

Query Parameters

  • DBserver (required):


    Return codes

  • 200:

  • 400: ID of a DBserver

  • 403: