Skip to content

Commit a61d35e

Browse files
choukdenchoukden
committed
Create Blog “hybrid-observability-service-–-part-3-enabling-the-monitoring-of-agentless-ssh-enabled-systems-in-hpe-greenlake-flex-solutions”
1 parent 01367ef commit a61d35e

File tree

1 file changed

+226
-0
lines changed

1 file changed

+226
-0
lines changed

‎content/blog/hybrid-observability-service-–-part-3-enabling-the-monitoring-of-agentless-ssh-enabled-systems-in-hpe-greenlake-flex-solutions.md

Lines changed: 226 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,226 @@
1+
---
2+
title: "Hybrid observability service – Part 3: Enabling the monitoring of
3+
agentless SSH-enabled systems in HPE GreenLake Flex Solutions"
4+
date: 2025-05-27T12:07:58.949Z
5+
author: Denis Choukroun
6+
authorimage: https://gravatar.com/avatar/f66dd9562c53567466149af06ae9d4f1?s=96
7+
disable: false
8+
tags:
9+
- hybrid-observability-flex-solutions
10+
- hybrid observability
11+
- OpsRamp
12+
---
13+
<style>
14+
li {
15+
font-size: 27px;
16+
line-height: 33px;
17+
max-width: none;
18+
}
19+
</style>
20+
21+
In [my previous blog post](https://developer.hpe.com/blog/hybrid-observability-service-%E2%80%93-part-2-initial-configuration-to-enable-the-discovery-of-resources-in-hpe-greenlake-flex-solutions/), I introduced the steps to install and configure a gateway collector appliance for a specific tenant client account in the hybrid observability service powered by HPE OpsRamp Software in HPE GreenLake Flex Solutions.
22+
23+
The gateway collector appliance is a prerequisite to enable the discovery of infrastructure devices in HPE GreenLake Flex Solutions before they can be monitored.
24+
25+
Continuing from the second part of this series, I’ll now explore:
26+
27+
* How to deploy an integration module to discover an agentless SSH-enabled server running Linux as the operating system.
28+
* How to apply a monitoring template to the agentless SSH resource to monitor it.
29+
30+
In the last Part <link to Part 4> of the blog series, I’ll explore the observability of physical devices and their monitoring using dashboards to visualize the collected metrics in charts.
31+
32+
## Applying integration modules and monitoring configuration to discover and monitor resources
33+
34+
### Integration modules
35+
36+
Once the gateway collector appliance is installed and configured to communicate with the hybrid observability service in the cloud, the next step is to install **Integration modules** to discover IT infrastructure devices. For example, compute, storage, and network equipment. Further, integration modules enable data exchange between the service in the cloud and IT infrastructure devices included in the HPE GreenLake Flex Solutions.
37+
38+
Once a resource is discovered, you can apply a **Monitoring Template** to periodically track the resource's performance, availability, and health metrics, based on configured metrics.
39+
40+
### Monitoring Templates
41+
42+
Monitoring is a method for periodically querying IT resources and forwarding resource metrics to the service for processing and analysis. [Monitoring Templates](https://glp.docs.opsramp.com/solutions/monitoring/template/) are used to apply standardized monitoring configurations to resources. These templates define the **metrics** and **thresholds** that will be monitored.
43+
44+
The hybrid observability service powered by HPE OpsRamp comes with a library of pre-configured **Global Monitoring Templates** that cover popular resource types. These built-in Global Monitoring Templates apply **automatically** through **Device Management Policies** to a wide range of resource types such as Operating System (Linux, Windows), compute servers, network devices, storage arrays, applications, virtualization and databases.
45+
46+
### Device Management Policies
47+
48+
[Device Management Policies](https://glp.docs.opsramp.com/platform-features/feature-guides/resource-management/) are rules that **automate** managing and monitoring resources after discovery.
49+
50+
There are predefined **Global Device Management Policies** available for common platforms and device types. These built-in policies are designed to help you **automatically** bind the Monitoring Templates to discovered resources based on matching criteria (for example, _Native Type = Linux_, _Operating System contains CentOS_, _Make = HPE_).
51+
52+
There might be some scenarios where you need to define a Monitoring Template and apply it either **manually** to a specific resource or **automatically** via a Device Management Policy to monitor a set of resources of the same type. For example, discovered agentless resources require a Monitoring Template to be created and applied manually or via a Device Management Policy to a single resource or a set of resources.
53+
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+
56+
### Agentless discovery and monitoring of SSH-enabled devices
57+
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+
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+
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+
64+
#### Requirements:
65+
66+
* A gateway collector appliance is installed and registered.
67+
* The gateway collector appliance has network access (through SSH protocol – typically on port 22) to connect to the target Linux server.
68+
* IP address of the target SSH-based machine(s).
69+
* SSH credentials (username and password) of the target machine.
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+
72+
#### Install the Linux agentless integration module in a client account
73+
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+
76+
1. To discover a compute resource, select the **client account**, then select **Setup** in the navigation bar, and select **Account** in the drop-down menu to navigate to the account details page.
77+
78+
2. Select the **Integrations** tile to access the Integrations App store and click **+ADD** to display all the integration applications available for the client account.
79+
80+
[img 1]
81+
82+
> **Note:** If this is your first integration module you want to install, click **+ADD** directly from the Integrations tile.
83+
84+
3. Filter the list of available integrations by a variety of **Categories** or use the **Search** feature. For agentless SSH-enabled devices, you can filter through category **OS** or in the Search field, type **SSH**.
85+
86+
[Img 2]
87+
88+
4. Choose the integration module to install the **Linux OS – Agentless (SSH)** by selecting **ADD**.
89+
90+
5. Navigate to the agentless-SSH configuration page. The first step in the process is to input **Basic Account Information**. Select **+ADD** at the right of the **Configuration** tab, then enter a **Name** for the configuration. For example, _Name = SSH Compute integration_.
91+
92+
6. In the **Host Name/IP Address** box, enter an IP address, or the hostname of the target agentless system.
93+
94+
7. Select the **SSH Credential** box and click **+ADD** to create new credentials to discover the agentless server. Specify:
95+
96+
* The credential name and a brief description.
97+
* The authentication type (typically Password) and appropriate credentials (username and password).
98+
* The SSH port (typically port 22).
99+
* Check the box “Secure”.
100+
* Finally, click ADD to create the SSH credential.
101+
102+
> **Note:** You can also select existing SSH credentials if one already exists and that applies to your resource.
103+
104+
[Img 3]
105+
106+
8. In **PERFORM ACTIONS**, select the **Manage Device** checkbox.
107+
108+
9. Next, define a **Discovery Schedule**. The schedule ensures that all resources and components inventory are in sync between the hybrid observability service and the agentless (SSH) server. You can select minutes, hourly, daily, weekly, or monthly schedule.
109+
110+
10. Now that all the configuration details are entered, select **ADD** to save the configuration of the integration module.
111+
112+
11. Click **NEXT** and **select** a collector profile, the gateway collector appliance that will be used to install the integration module and discover the agentless resource.
113+
114+
12. Click **FINISH** to complete the installation of the integration module and initiate the resource discovery.
115+
116+
13. Select the Integrations tile, and click on the **Linux OS – Agentless (SSH)** tile to check the status of the agentless SSH integration module:
117+
118+
* The gateway collector appliance displays with the status **RUNNING**.
119+
* Select the gateway collector appliance to check the status of the agentless SSH integration module. The discovery status should be **Completed**.
120+
* Based on your discovery schedule, the value for the devices might be set to **0**. In this case, select the ellipsis (...) on the right and select **Discover** to discover the device manually.
121+
* Click **DONE**.
122+
* Connect again to the SSH integration module and select the gateway collector appliance. You should see now a device discovered.
123+
* Click on the **1** for the devices to visualize the resource information for the Linux server. Notice the status is **UNDEFINED** (color indication brown). The reason is that **no** default Global Monitoring Template is automatically assigned to an agentless SSH-enabled system. In the next step, you will create a monitoring template and assign it to the agentless device.
124+
125+
[Img 4]
126+
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+
129+
#### Define a monitoring template and assign it to agentless devices
130+
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+
133+
The built-in Global Monitoring Templates are **not editable**. **Copy** an appropriate built-in Global Monitoring Template and customize the _metrics_, _thresholds_, and _resource availability monitor_ for the most important metric(s) for the resource to meet the IT operational needs for the client account.
134+
135+
> **Note:** The [Resource Availability documentation](https://glp.docs.opsramp.com/solutions/availability/resource-availability/) refers to the uptime and operational status of a monitored resource. It tracks whether the resource is running or experiencing downtime based on the metrics with the availability monitor applied.
136+
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+
139+
Let’s see how to create a Monitoring Template and the methods to assign it to the discovered agentless Linux device(s).
140+
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:
141+
142+
1. Select a client account.
143+
144+
2. Go to **Setup > Setup > Monitoring > Templates** and click **Advanced**.
145+
146+
3. Search for Scope _Global Templates_ and enter _gateway_ or _gateway - linux_ as the Template Name. Then click **Search** at the bottom of the **Advanced** search.
147+
148+
> **Note:** This feature will be made available under **Setup > Account > Monitoring** in an upcoming HPE OpsRamp releases.
149+
150+
[Img 5]
151+
152+
4. Select the **latest version** of the Global Monitoring Template **Gateway - Linux OS Performance Remote Monitoring** available. You can click the arrow on the left of the template to visualize the metrics and thresholds.
153+
154+
[Img 6]
155+
156+
5. Select the **Template** checkbox. Click **Copy** to clone the template and click **Yes** to duplicate the template.
157+
158+
6. Select the **client account**, give a **Name** to your template. Use the client account name in the _Template Name_ to identify the template for a particular client account easily. Click **Save**.
159+
160+
7. To list the Monitoring Templates for the Client Account, go to **Monitoring > Templates > Advanced Search >**, select **Client Templates** for the _Scope_. You can now customize the template to adjust some parameters such as the _tags_, metrics such as the **warning** or **critical thresholds**, and the **availability monitor** per your IT operational requirements.
161+
162+
8. To monitor the resource, enable an **Availability Monitor** for a metric (for example, _os.uptime_).
163+
164+
* Select the cloned Monitoring Template and click **Edit** at the top right of the template.
165+
* Click **Next** at bottom of the page and select the metric that is more important for the resource by clicking on the pencil to the right of the metric.
166+
* Check the **Apply Availability Monitor** checkbox and click **Update**.
167+
* You can also modify the warning and critical thresholds of any metric per your operational requirements.
168+
169+
[Img 7]
170+
171+
9. Finally, click **Save** to save the Monitoring Template.
172+
173+
You can now assign the Monitoring Template to the agentless resource either manually or via a Device Management Policy.
174+
175+
You may want to assign the Monitoring Template manually if you have a single resource. If you are planning to monitor a set of resources of the same type, it is recommended that you apply the Monitoring Template via a **Device Management Policy**. The policy will automatically apply the resource policy to the resources based on a set of filter criteria you specify in the policy.
176+
177+
Let’s walk you through the two methods to apply the Monitoring Template to a resource:
178+
179+
**Method 1 — Manual assignment to a particular resource**
180+
181+
1. Select the **client account** and go to **Infrastructure > Search**
182+
183+
2. Select your Linux server.
184+
185+
3. Check the checkbox of your server, click **ACTIONS** on the right, and select **Assign Templates**.
186+
187+
4. Search for the **Monitoring Template** you have just created, check the box for the Monitoring Template, and click **ASSIGN TEMPLATE** button.
188+
189+
**Method 2 — Automatic assignment to a set of resources via a Device Management Policy**
190+
191+
1. Select the **client account** and from the navigation bar go to **Setup > Setup > Resources > Device Management Policies**.
192+
193+
> **Note:** This feature will be made available under **Setup > Account > Monitoring** in an upcoming HPE OpsRamp releases.
194+
195+
2. If it is the first time you want to create a Device Management Policy, click **Create New**. If you have already created policies, click the option **+Add** to create a new Device Management Policy for the agentless SSH system. The Device Management Policy page is displayed.
196+
197+
3. Ensure the **Client** option is selected for the **Scope** and the appropriate **client account** has been selected. Give a policy **Name** (for example _Agentless Linux Monitoring Policy_) and ensure the **Add members automatically using filter criteria** checkbox is checked.
198+
199+
4. Select one or more **Filter Criteria** that apply to your agentless device(s) and click **Show Matching Members** to ensure the resources matching the filter criteria are the expected devices. For example, you can filter on _Native Type_ and _Make_ of the device as shown here:
200+
201+
[Img 8]
202+
203+
5. In the **Perform Actions** section, select the **Assign Monitoring Templates** checkbox. A list of available monitoring templates is listed. Select the Monitoring Template you previously created and click the right arrow to move it to the **Assigned Monitoring Templates** column on the right.
204+
205+
6. Click **Save & Run Now** to assign the policy to the resources matching the filter criteria. The policy will apply to all resources that match the filter criteria you specified in the policy.
206+
207+
7. After a few minutes, check the agentless SSH device in **Infrastructure > Search** and select the device to check the status and the metrics. The status should now be **UP** (color indication is green) and you can start visualizing the metrics.
208+
209+
[ img 9]
210+
211+
[img 10]
212+
213+
214+
## Summary
215+
216+
This blog post walked you through the steps to set up the hybrid observability service powered by HPE OpsRamp. With this service enabled, you can discover, monitor, and observe the health, performance, and availability of an agentless SSH-enabled system.
217+
218+
In my last part <link to Part 4> of this blog series, I’ll dive into the observability of a physical server and a storage array as we continue the journey to set up the hybrid observability service to discover and monitor physical IT infrastructure devices included in the HPE GreenLake Flex Solutions contract.
219+
220+
To resolve issues with HPE GreenLake Flex Solutions or hybrid observability service powered by HPE OpsRamp, contact the support team. While logged in to your HPE GreenLake workspace:
221+
222+
1. Click **Help & Support**.
223+
2. Under **Help**, select **OpsRamp** or **HPE GreenLake Flex Solutions**.
224+
3. Click **Create New Case**.
225+
226+
If you still have any questions regarding the hybrid observability service configuration, join the [HPE Developer Community Slack Workspace](https://developer.hpe.com/slack-signup/) and start a discussion on our [#hpe-greenlake-flex-observability](https://hpedev.slack.com/archives/C08K4GV7YN5) Slack channel.

0 commit comments

Comments
 (0)