Docs > Deployment & Installation > On-Prem Deployment & Installation > Deployment on Existing Kubernetes Cluster
1. Getting Started with vuSmartMaps™
3. Console
5. Configuration
6. Data Management
9. Monitoring and Managing vuSmartMaps™
vuHealthAgent is a data collection agent used on systems running Solaris and AIX for
The collected metrics and heartbeat data are sent to the vuSmartMaps data collection node or the shipper.
The node on which the agent is installed should be allowed to connect to the vuSmartMaps data collector/shipper IP and TCP/UDP port configured for the agent.
The default ports on which data is sent are
tar -xvf vuhealthagent-python.tar
./install
/home/$USER – The installation will create vuHealthAgent directory inside /home/$USER/
/home/$USER/agents – The agents directory should exist in the system.
Login with sudo user or root user and run the below commands based on your os.
Solaris:
ln -s (VUHEALTHAGENT_HOME)/etc/init.d/vuhealthagent-boot /etc/rc3.d/S99vuhealthagent
ln -s (VUHEALTHAGENT_HOME)/etc/init.d/vuhealthagent-boot /etc/rc3.d/K99vuhealthagent
AIX:
ln -s (VUHEALTHAGENT_HOME)/etc/rc.d/init.d/vuhealthagent-boot /etc/rc.d/rc3.d/S99vuhealthagent
ln -s (VUHEALTHAGENT_HOME)/etc/rc.d/init.d/vuhealthagent-boot /etc/rc.d/rc3.d/K99vuhealthagent
Note: (VUHEALTHAGENT_HOME) is the directory where vuHealthAgent is installed.
After the installation, the script will ask for the configuration of the installed agent. press y to configure the agent on the go or press n to skip the configuration and you have to manually configure it by updating (VUHEALTHAGENT_HOME)/conf.d/config.json
The configuration will update the following attributes:
Note: A general assumption is agents are installed with the knowledge of the exact collection method and listening port setup at the vuSmartMaps end. If this information is not yet known, contact Vunet support.
This part of the configuration contains options to configure targets and ports to determine a given service availability using periodic heartbeat.
The agent supports service heartbeat only.
List of dictionary blocks, each containing the following mandatory fields:
Sample Heartbeat Block:
“heartbeat”: [
{
“name”: “Heartbeat”,
“hosts”:
[
“www.vunetsystems.com:80”,
“www.vunetsystems.com:443”,
“127.0.0.1:1090”
],
“interval”: 120
}
],
This part of the configuration is used to enable the list of system metrics to collect from the node. Each block will contain the following mandatory fields. Multiple blocks can be created with varying collection intervals as required.
Currently, supported modules are:
Sample Health Metrics Block:
“health”: [
{
“name”: “Health collection”,
“interval”: 180,
“modules”:
[
“load”,
“socket”,
“core”,
“cpu”,
“process”,
“memory”,
“disk”,
“diskio”,
“network”
]
}
],
OHS metrics can be collected through the following mechanisms
Configuration
“ohs_config”:
{
“ipaddress”: “127.0.0.1”,
“module”: “dms”,
“port”: “7777”,
“is_SSL_enabled”: “no”
}
ipaddress – The ip address on which OHS publishes status metrics
module – The module used to publish the OHS status metrics
dms/server-status
port – The port on which the OHS listens
is_SSL_enabled – Is OHS running or https/http. Mark it yes/no
Note: Refer to the reference configurations available along with the agent package.
These options allow you to filter out all processes that are not in the top N by CPU or memory, in order to reduce the number of documents created.
Configuration
“process_top_n”:
{
“by_cpu”: 0,
“by_mem”: 0
}
If both the `by_cpu` and `by_mem` options are used, the union of the two sets is included.
by_cpu – How many processes to include from the top by CPU. The processes are sorted by the `system.process.cpu.total.pct` field.
by_mem – How many processes to include from the top by memory. The processes are sorted by the `system.process.memory.rss.bytes` field.
This part of the configuration is used to execute commands on the target server and collect metrics. Each block will contain the following mandatory fields. Multiple blocks can be created with varying collection intervals as required.
Following optional fields are also supported:
Sample Command Block:
“command”: [
{
“name”: “file-listing”,
“cmd” : “cd /tmp; ls -lrt”,
“collect_output”: true,
“interval”: 60
}
]
Note:
Logs are written to (VUHEALTHAGENT_HOME)/log/vuhealthagent.log by default.
The default log level is DEBUG. This can be changed in
Solaris:
(VUHEALTHAGENT_HOME)/etc/init.d/vuhealthagent start
(VUHEALTHAGENT_HOME)/etc/init.d/vuhealthagent stop
(VUHEALTHAGENT_HOME)/etc/init.d/vuhealthagent status
AIX:
(VUHEALTHAGENT_HOME)/etc/rc.d/init.d/vuhealthagent start
(VUHEALTHAGENT_HOME)/etc/rc.d/init.d/vuhealthagent stop
(VUHEALTHAGENT_HOME)/etc/rc.d/init.d/vuhealthagent status
The vuHealthAgent package comes with an uninstall script to uninstall.
To uninstall, simply go to the extracted setup directory and run
Uninstallation is then complete.
Browse through our resources to learn how you can accelerate digital transformation within your organisation.
VuNet’s Business-Centric Observability platform, vuSmartMaps™ seamlessly links IT performance to business metrics and business journey performance. It empowers SRE and IT Ops teams to improve service success rates and transaction response times, while simultaneously providing business teams with critical, real-time insights. This enables faster incident detection and response.