Skip to main content
Version: NG-3.1

URL Availability

Introduction

URL Availability Monitoring checks that your web resources, identified by URLs, are consistently accessible or not.

Getting Started

Compatibility

URL Availability O11ySource supports monitoring the availability of URLs for your web resources.

Data Collection Method

vuSmartMaps collects URL Availability metrics through a data collector deployed within the vuSmartMaps platform, which uses an HTTP client to measure availability, response time, and HTTP response metadata.

Prerequisites

Inputs for Configuring Data Source

  • Group: A label to organize related URLs (for example, “Payments” or “Customer Portal”).
  • URL Details: URL configuration.
  • URL: Enter the website URL, e.g., 'https://www.example.com'.
  • Period (in seconds): The period should be between 60 and 3000 seconds.
  • Response Timeout (in seconds): Maximum time to wait before marking the check as failed (for example, 5–10 seconds).
nan

Firewall Requirement

To collect data from this O11ySource, ensure the following ports are opened:

Source IPDestination IPDestination PortProtocolDirection
vuSmartMaps Collection/Ingress node IPTarget URL80*/443*TCPOutbound

*Before providing the firewall requirements, please update the port based on the customer environment.

Configuring the Target

Ensure the URL address(es) are valid and reachable from the vuSmartMaps Collection/Ingress node.

Configuration Steps

Metrics Collected

NameDescriptionData Type
nameName of the request or transaction, often used to identify it.String
timestampThe exact date and time when the event or request occurred.DateTime64
hostThe hostname or IP address of the server handling the request.String
resultThe result or outcome of the transaction, typically a status message.String
serverThe specific server that processed the request.String
status_codeAlias of http_response_code (backward compatibility).String
content_lengthThe size of the content returned in the response, in bytes.UInt32
methodHTTP method used for the request, e.g., GET, POST, PUT, DELETE.String
http_response_codeHTTP status code returned by the endpoint (e.g., 200, 404, 500).UInt32
response_timeThe time taken by the server to respond, in milliseconds.Float32
result_codeA code representing the result of the operation (could be an application-specific code).String
result_typeThe type or category of result, often indicating success, failure, etc.String
tenant_idID representing the tenant or customer making the request.UInt32
bu_idID representing the business unit involved in the transaction.UInt32
@timestampString representation of the timestamp for logging or debugging purposes.String
target_stateTo check the status of the URLString
content_transfer_timeThe time taken to transfer the response data from the server to the client after the request is processed.Float32
server_processing_timeThe duration spent by the server to process the client's request and generate a response.Float32
tcp_connection_timeThe time required to establish a TCP connection between the client and the server.Float32
tls_handshake_timeThe time taken to complete the TLS (or SSL) handshake process, which is needed to establish a secure connection.Float32
dns_lookup_timeThe time it takes to resolve the domain name to an IP address through DNS (Domain Name System) lookup.Float32