Skip to content

Home

Introduction

Development

IDEs

Services

API Explorer

Releases

Release notes

Martini Runtime

Martini Desktop

Martini Online

Feature requests

Bug reports

Searching for invoke documents

While intended for API monetization, data in the invoke monitor search index and database can still be used for applications that need statistical accounts of service invokes. This data can be used for the auditing and analysis of service invocations. On this page, we will discuss the different methods you can use in order to preview or obtain service invocation data for your integrations.

Using the user interface

Of all interfaces compatible with Martini, only the Martini Runtime Admin UI demonstrates querying capabilities against the invoke monitor search index. In particular, searches can be done through interface elements located at the static search bar, seen at the top of the Martini Runtime Admin UI.

Viewing all documents

Go to the static search bar located at the top of the Martini Runtime Admin web interface. Select Monitor from the dropdown, and click the search button to go to the Monitor page.

The Monitor page will display all documents residing in the instance's Monitor search index. To update displayed results, refresh the page.

Accessing the Monitor page

Viewing document details

Viewing invoke document details

To view the details of a specific Monitor document, click the document's ID from the table displayed in the Monitor page. The details for the chosen document will appear on the right side of the page.

Simple filter

Monitor search bar

Use the search bar to look for invoke documents containing field values that match the provided input string. Type the text to match in the search bar and then press .

Facet filter

Monitor facet filter

You can also filter invoke documents using facets. Click the facet field you want to filter by, and then select a value from the appearing dropdown to filter documents using the selected facet. You'll notice next to each facet is a number. This number is the number of documents in the invoke monitor search index that match the facet.

Advanced filter

Monitor advanced filter

If you need finer-grained searches, you can use the Advanced Filter form. This type of search allows you to specify a value-to-match per field. Click the inverted triangle beside the search button to make the form appear.

Using RESTful web services

As with the other search indices, the invoke monitor search index can be queried and managed via the Solr Search API. Simply ensure the following path parameters are substituted when sending requests:

Parameter name Value
package core
core invoke_monitor

For example:

1
/esbapi/v1/solr/core/invoke_monitor/

Using one-liners

To query the Invoke monitor search index in Gloop, create an invoke step (preferred) or Gloovy step calling any of the search methods belonging to MonitorMethods. Your step should roughly look like this:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
GloopModel searchMonitor( query,
                          id,
                          trackerId,
                          packageName,
                          serviceName,
                          user,
                          userGroups,
                          endpointName,
                          endpointType,
                          url,
                          remoteAddress,
                          country,
                          location,
                          success,
                          responseTime,
                          startDate,
                          endDate,
                          minCost,
                          maxCost,
                          int pageSize,
                          int page )

MonitorMethods has other utility methods for your Invoke monitor-related needs

MonitorMethods contains convenience methods for:

  • Managing and retrieving monitor rules
  • Fetching the billing details of your users