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
The Service Monitor O11ySource supports monitoring services on any operating system, provided the service TCP port is accessible.
Data Collection Method
vuSmartMaps collects Service Monitor metrics through a data collector deployed within the vuSmartMaps platform, which uses net_response plugin to retrieve performance and health metrics.
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.
Applications
Firewall Requirement
To collect data from this O11ySource, ensure the following ports are opened:
| Source IP | Destination IP | Destination Port | Protocol | Direction |
|---|---|---|---|---|
| All vuSmartMaps Collection/Ingress node IP | IP address of the device | 443* | TCP | Bidirectional |
*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
Metrics Collected
| Name | Description | Data Type |
|---|---|---|
| @timestamp | The original timestamp as a string, typically the raw timestamp when the event was logged. | String |
| timestamp | The timestamp with precise date and time (up to fractional seconds) indicating when the event occurred. | DateTime64 |
| ServiceHost | The name or identifier of the service host where the event occurred. | String |
| name | name of the service | String |
| host | Hostname or IP address where the event was generated or logged. | String |
| tenant_id | Identifier for the tenant, useful in multi-tenant environments to distinguish between different clients. | LowCardinality(String) |
| bu_id | Business Unit identifier, indicating the division or unit responsible for the event or asset. | LowCardinality(String) |
| vublock_name | Name of the virtual block or segment, typically used in storage or networking contexts. | String |
| topic_name | Name of the topic, often related to messaging systems like Kafka or similar. | LowCardinality(String) |
| port | Network port associated with the event, indicating the communication channel used. | UInt32 |
| target_state | The desired or expected state of the target (e.g., up, down, active). | LowCardinality(String) |
| UpTimePct | Percentage of uptime for the monitored service or resource. | Float32 |
| average_rtt | The average round-trip time (RTT) for packets during the session. | Float32 |
| maximum_rtt | The maximum round-trip time recorded during the session. | Float32 |
| minimum_rtt | The minimum round-trip time recorded during the session. | Float32 |
| pkt_loss_pct | Percentage of packet loss calculated during the event. | Float32 |
| DownTimePct | Percentage of downtime for the monitored service or resource. | Float32 |
| jitter | Variation in packet arrival time, which can affect network performance. | Float64 |
