Retrieving problems of a tier member

The GET method of the Problems API retrieves the transaction performance and availability problems for a specified time, tier, and application. The problems are as listed in the Application metrics and problems topic.

The API contains the following topics:

API overview

Method—GET

Request parameters—timestamp, memberId, application, tier

API registration

Use the following URL to register the API:

https://portalHost:portalPort/portal/rest/problems

Replace the following entries, as required:

Entry	Description
https	Protocol used to send the request
portalHost	Host name or IP address of the App Visibility portal
portalPort	Communication port number of the App Visibility portal. The default port number is 8100.

Request parameters

Entry	Description	Mandatory
timestamp	Epoch time stamp of the problem, in milliseconds, from which to take the data collection Use a time stamp converter, such as http://www.epochconverter.com/, to generate the value.	Yes
memberId	One or more identifying string (automatically assigned) of the tier members, that is, the application server Example: memberId=id1&memberId=id2&memberId=id3	No
application	Identifying string (automatically assigned) of the application	Yes
tier	Tier by which to limit the response: WEB, BUSINESS, SYNTHETIC, USER, NETWORK, or DB.	Yes

URL example

https://clm-pun-014433:8100/portal/rest/problems?timestamp=1441692600000&tier=WEB&application=8D720C2D&memberId=VW-TLV-AD-QA18

Sample JSON response

Response content

The response shows all open problems for the specified time, tier, application, and (optionally) tier member.

Object	Description
severity	Severity of problem or event: CRITICAL, MINOR
memberId	Identifying string (automatically assigned) of the tier member, that is, the application server
eventType	Type of event or problem, as listed in the Application-metrics-and-problems topic
unit	Unit of the metric Not applicable to latency violations or errors
metricType	Type of metric
extraInfo appCtxID appName appID	Application information: Object for internal use Application name Identifying string (automatically assigned) for the application
creationDate	Epoch date, in milliseconds, that the event began
actualValue	(Latency violations or erros) -1 (no actual value to provide) (Network, user, or server metrics) Numeric value, such as percentage of impacted users
expirationDate	Epoch date, in milliseconds, that the event is closed or will be closed automatically
thresholdValue	(Latency violations or errors) -1 (not applicable) (Network, user, or server metrics) Threshold value
problemId	Identifying string (automatically assigned) for the problem