logs

URI

Supported methods

Parent resource

Introduction

logs resource is used to get the system log information of the server. System log information is divided into 4 levels: Error, Warning, Info and Debug.

Supported Methods:

GET: Gets the system log information of the service component.
HEAD: Check whether the logs resource exists. or to access the logs resource.

Supported output formats: rjson, json, html, xml.

Resource hierarchy

HTTP request methods

Implement the HTTP request on the following URI, where supermapiserver is the server name, with rjson being the output format.

http://supermapiserver:8090/iserver/manager/logs.rjson

GET request

Gets the system log information of the service component.

Request parameter

When implementing GET request on the logs resource, the following parameters are contained in URI, used to control the log level and entry number.

Name	Type	Description
logLevel	String	[Optional parameter] Log level. The value can be ERROR, WARN, INFO, DEBUG or ALL. ALL represents t get all the log levels (ERROR, WARN, INFO, DEBUG) information. Default is INFO.
count	int	[Optional parameter] Entry number. The latest N records. Default is 20.

Response structure

The response result is the log record array. The response structure is as follows:

Field	Type	Description
className	String	The class name.
date	String	The log time.
line	String	The separator, i.e., "-".
logLevel	Level	the log level.
message	String	Summary.
packageName	String	The package name.
stackTrace	String	The stack information, i.e., the error tracking information.

Response example

Implement GET request on logs resource http://localhost:8090/iserver/manager/logs.rjson?logLevel=INFO&count=5. You can get the latest 5 logs in INFO log level. The returned rjson format representation is as follows:

[ { "className": null, "date": "2014-10-16 11:18:12", "line": null, "logLevel": { "name": "INFO", "priority": 200 }, "message": "Business component data-rest-jingjin was created successfully", "packageName": null, "stackTrace": "" }, { "className": null, "date": "2014-10-16 11:18:11", "line": null, "logLevel": { "name": "INFO", "priority": 200 }, "message": "Service provider rest-jingjin was created successfully", "packageName": null, "stackTrace": "" }, { "className": null, "date": "2014-10-16 11:15:55", "line": null, "logLevel": { "name": "INFO", "priority": 200 }, "message": "Destroy service instance data-jingjin/wcs111. ", "packageName": null, "stackTrace": "" }, { "className": null, "date": "2014-10-16 11:15:55", "line": null, "logLevel": { "name": "INFO", "priority": 200 }, "message": "Destroy service instance data-jingjin/rest. ", "packageName": null, "stackTrace": "" }, { "className": null, "date": "2014-10-16 11:15:55", "line": null, "logLevel": { "name": "INFO", "priority": 200 }, "message": "Destroy service instance data-jingjin/wcs112. ", "packageName": null, "stackTrace": "" } ]

HEAD request

Asks for the response identical to the one that would correspond to a GET request, but without the response body. This is useful for retrieving meta-information written in response headers, without having to transport the entire content. The meta-information includes the media-type, content-encoding, transfer-encoding, content-length, etc.

HEAD request can be used to check if the logs resource exists, or if the logs resource can be accessed by clients. It can also determine if the logs resource supports an output format <format> if performed on a URI with .<format> included.