Skip to content

Home

Introduction

Development

Overview

IDEs

Services

Service manager

API Explorer

Monitor document

TORO Integrate produces a document per service invoke which contains the particulars of the service call. Every document is later indexed to make it queryable. The following table describes the searchable properties of each of these documents:

Field Name Data Type Description
id String The auto-generated identifier for the document.
ruleId long The identifier of the rule that first matched the request1. This is set to -1 if there is no positive match.
timeReceived Date The time the service call was made in yyyy-MM-dd'T'HH:mm:ss.SSSZ format.
trackerId String The identifier of the document's counterpart in the Tracker search index, if it exists2.
packageName String The name of the package which handled the request.
endpointName String The name of the endpoint that invoked the service.
endpointType String The type of endpoint over which the service was invoked.
apiGroup String The name of the group the caller (user) belongs to.
serviceName String The name of the service that was invoked.
url String The invoke URL.
user String The username of the user who invoked the service.
success boolean Flag indicating whether the service was successfully executed or not.
cost Double The cost of invoking the service.
responseTime long The duration of the service call.
location String The originating request's coordinates.

  1. Because rules can have overlapping scopes, there are times when multiple rules are applicable to a single service invocation. However, TORO Integrate will check all rules (based on their priority), and use the first match. 

  2. Because logging with Tracker is optional.