Skip to main content
Version: NG-2.14

Service Monitor

Introduction

Service Monitor is a go-to solution for monitoring services, providing real-time insights into the availability of diverse URLs to ensure uninterrupted operation.

Getting Started

Compatibility

Service Monitor O11ySource is compatible to monitor services running in any of the operating systems as long as the TCP Port used by service is accessible

Data Collection Method

vuSmartMaps collects the monitoring data for this O11ySource using an internal data collector. This data collector collects data based on the source configuration.

Prerequisites

Inputs for Configuring Data Source

  • Name: Name of the source.
  • Service: Services to be monitored. Ex: www.google.com:443
  • Period [in seconds]: How frequently data is gathered. The period should be between 60 seconds – 3000 seconds.

Firewall Requirement

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

Source IPDestination IPDestination PortProtocolDirection
All vuSmartMaps IPsIP address of the device-TCPBidirectional

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

Configuring the Target

The port opening should be done for the services to be monitored and should be accessible to vuSmartMaps.

Configuration Steps

  • Enable the O11ySource.
  • Select the Sources tab and press the + button to add a new instance of the service to be monitored.
  • Add 'Name', 'Service', 'Period' and 'Protocol' as per requirement.
  • Click on Save and Continue to create the instance.

Metrics Collected

NameDescriptionData Type
@timestampThe original timestamp as a string, typically the raw timestamp when the event was logged.String
timestampThe timestamp with precise date and time (up to fractional seconds) indicating when the event occurred.DateTime64
ServiceHostThe name or identifier of the service host where the event occurred.String
namename of the serviceString
hostHostname or IP address where the event was generated or logged.String
tenant_idIdentifier for the tenant, useful in multi-tenant environments to distinguish between different clients.LowCardinality(String)
bu_idBusiness Unit identifier, indicating the division or unit responsible for the event or asset.LowCardinality(String)
vublock_nameName of the virtual block or segment, typically used in storage or networking contexts.String
topic_nameName of the topic, often related to messaging systems like Kafka or similar.LowCardinality(String)
portNetwork port associated with the event, indicating the communication channel used.UInt32
target_stateThe desired or expected state of the target (e.g., up, down, active).LowCardinality(String)
UpTimePctPercentage of uptime for the monitored service or resource.Float32
average_rttThe average round-trip time (RTT) for packets during the session.Float32
maximum_rttThe maximum round-trip time recorded during the session.Float32
minimum_rttThe minimum round-trip time recorded during the session.Float32
pkt_loss_pctPercentage of packet loss calculated during the event.Float32
DownTimePctPercentage of downtime for the monitored service or resource.Float32
jitterVariation in packet arrival time, which can affect network performance.Float64