You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/blog/hybrid-observability-service-–-part-3-enabling-the-monitoring-of-agentless-ssh-enabled-systems-in-hpe-greenlake-flex-solutions.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,23 +53,23 @@ There might be some scenarios where you need to define a Monitoring Template and
53
53
54
54
> **Note:** You can check the Enable Global Policies option for the client account to automatically apply a Global Device Monitoring Policy, **if one exists**, for a resource such as the SSH-enabled system. In this post, I’ll explore how to discover the SSH-enabled system, create a monitoring template and assign it to the system to enable its monitoring.
55
55
56
-
###Agentless discovery and monitoring of SSH-enabled devices
56
+
## Agentless discovery and monitoring of SSH-enabled devices
57
57
58
58
Let us start by deploying an Integration module and creating a Monitoring Template to discover and monitor an [agentless SSH-enabled system](https://glp.docs.opsramp.com/integrations/os/linux-os-agentless-discovery/).
59
59
60
60
The hybrid observability service supports agentless monitoring. Agentless monitors use the **gateway collector appliance** to discover resources via SSH and monitor IT infrastructure agentless resources to track their health, performance, and availability.
61
61
62
62
The SSH Agentless Integration module discovers Linux/Unix-based systems **without installing an agent**, by securely connecting to the device over SSH via the gateway collector appliance. The Monitoring Template then needs to be assigned to the target agentless system for monitoring.
63
63
64
-
####Requirements:
64
+
### Requirements:
65
65
66
66
* A gateway collector appliance is installed and registered.
67
67
* The gateway collector appliance has network access (through SSH protocol – typically on port 22) to connect to the target Linux server.
68
68
* IP address of the target SSH-based machine(s).
69
69
* SSH credentials (username and password) of the target machine.
70
70
* A Monitoring Template and Device Management Policy to monitor the target resource through the gateway collector appliance and collect data for monitoring the metrics and resource availability.
71
71
72
-
####Install the Linux agentless integration module in a client account
72
+
### Install the Linux agentless integration module in a client account
73
73
74
74
As Partner Administrator, let’s install an **agentless SSH Integration module** to discover an HPE ProLiant server added in the HPE GreenLake workspace devices inventory. This compute server runs the Linux operating system. The Linux OS agentless SSH Integration module facilitates agentless discovery of SSH-enabled devices using the gateway collector appliance. Here is the procedure:
75
75
@@ -126,7 +126,7 @@ As Partner Administrator, let’s install an **agentless SSH Integration module*
126
126
127
127
14. Select the server's name to collect attributes of the Linux server device such as the _Operating System (CentOS)_, _Native type (Linux)_ and _Make (HPE)_. You will need this information in the next step to configure the filter criteria for the monitoring policy of the agentless system.
128
128
129
-
####Define a monitoring template and assign it to agentless devices
129
+
## Define a monitoring template and assign it to agentless devices
130
130
131
131
When an agentless system is discovered through the gateway collector appliance using the appropriate Integration module, you need to define and apply a **Monitoring Template** for the gateway collector appliance to monitor the device for a specific client account.
132
132
@@ -137,6 +137,7 @@ The built-in Global Monitoring Templates are **not editable**. **Copy** an appro
137
137
You can then manually assign the customized Monitoring Template to a particular resource, or via a **Device Management Policy** to automatically bind your Monitoring Template to the discovered agentless devices.
138
138
139
139
Let’s see how to create a Monitoring Template and the methods to assign it to the discovered agentless Linux device(s).
140
+
140
141
The gateway collector appliance discovered the agentless SSH system. It will monitor the agentless SSH system using a Monitoring Template. Therefore, let’s select a Global Monitoring Template with a name that contains the word _gateway_ and **clone** this template:
0 commit comments