Services Log and History

Presentation

This view will display the list of all registered Services (ie HTTPService, WebService and RemoteObject), and an history of their requests.
Once again, this view works in real time, and will allow you to observe whats happening at the service level, to check out parameters sent and results returned

To activate this view, select the "HTTP Services" tab of the console, but for that you will have to integrate our patch library into your project, as described in Remote services debugging important note.

In this view, we have:

• The left pane that displays a list of all registered services, through Cairngorm ServiceLocator
  • Service number
  • Total service duration in ms(in terms of cumulative time, which does not equal to elapsed time as several queries may be runned in parallel)
  • Name of the service as it has been registered in the ServiceLocator
• The center pane show the history of all send queries for the selected service:
  • Number of the query for this service
  • Duration of the query, in ms
  • Start point for the query: Class name, method and line number
  • the URL that has been requested
• The right pane is for inspection of the service important parameters and values:
  • result: this is the result found in the ResultEvent dispatched by service upon return.
  • parameters: for a GET request, there may be extra parameters.
  • request: for POST requests, it is the content of the request that has been submitted
  • headers: custom headers, if any
• The lower pane, as usual, displays the stack trace for the selected service run.

To get more information about this view, please refer to the reference guide

Monitoring Services Activity

With real world application, connected to a back end server, you are likely to have a lot of service calls, and also maybe different services (such as PrintService, LoginService, and so on)
You will be able to monitor services activity in real time, just by leaving the HTTPService tab opened and watching (note that all events will be registered, even if the console is closed or not started)

Unfortunately, with this very simple demo application, there is only a single service, that is called only once, so you will have to integrate the console into an application of your to really see the services in action.

The screenshot below shows how the console looks like with a big application, with several services and many different calls: