Risks, Limitations and Assumptions

  • No provision to add url credentials as optional. Hence it does not support URL credentials.
  • Monitoring support is provided only for HTTP/HTTPs endpoint url and there is no support for IP addresses
  • Encrypted end point URL is used as signature(MoId). Hence if user modified already provided URL, old resource will get deleted and new resource will be created with edited URL.
  • As of now, using URL extracted Host name as Resource Host Name and using Profile name as Alias name.
  • As of now, using Native Resource Type as Metric instance HTTP Endpoint Probe application will send metric data to cloud only if it receives metric success flag as true from cpp executable. In case of any failures/errors OR when conditions(i.e, ResContentShouldContain/ResContentShouldNotContain etc..) given in configurations doesn’t match, SDK app will receive metric success flag as false from cpp executable which results in gaps in metric data.
  • This application has dependency with Gateway OS. As of now, we are using Ubuntu 14 made cpp executable. Moving forward if gateway OS is upgraded, there might be chance of the application crashing.
  • As of now below are the mentioned supported metrics:
    • endpoint_url_response_Time
    • endpoint_url_response_LookUpTime
    • endpoint_url_response_PreTransferTime
    • endpoint_url_response_StartTransferTime
    • endpoint_url_response_ConnectTime
    • endpoint_url_response_RedirectTime.
  • Support for synthetic.response.appconnecttime metric is not provided.
  • We have published the metrics with the timestamp provided in the cpp executable response.
  • In additional configurations, Postdata field should be a valid data string with escape character.
  • Base URL + UrlPath should be a valid endpoint URL.
  • In additional configurations, Method should be a valid request methods(GET, POST, PUT, PATCH..). If you are given invalid then it takes by default as ‘GET’.