HTTP Parameters for Client Monitoring

You can request monitoring metrics as part of any request that returns a client status object or a collection of client status objects.

Metrics data is available for ordinary application clients and also for TIBCO FTL component clients, such as bridges, eFTL servers, and persistence servers.

Syntax Description
monitoring=true Optional.

When present, the response includes monitoring metrics data as the value of the JSON attribute monitoring.

Example JSON Response

{
  "app_instance":"default",
  "app_name":"tibrecvex",
  "host":"ree",
  "id":11055,
  "ip":"10.101.2.226",
  "last_contact":"Feb 26, 2016 1:27:00 PM",
  "last_contact_delta":43658,
  "monitoring":{
    "id":11055,
    "series":[
      {
        "avg":"68,425,328.673",
        "context":"client_transport_0_1456246848935",
        "description":"Bytes Sent",
        "id":32,
        "last":"68,469,297",
        "max":"68,469,297",
        "min":"68,469,297",
        "samples":1,
        "semantic":"VALUE",
        "total_samples":6,
        "trend":1,
        "type":"bytes_sent",
        "units":""
      },
      ...