Page History

...

This article describes the configuration of r_keeper_7 monitoring via Zabbix system.
The monitoring allows the user to keep track of relevant metrics and be notified of exceeding critical measure values.

...

For monitoring purposes, you will need a Zabbix server. At the time of this writing, only versions for Linux were available. They can be downloaded from the official site. Installation instructions are available there, as well.

...

A Zabbix agent should be installed on each computer running the r_keeper 7 system. You can download it from the official site. We well describe installation on Windowson Windows.

1. Launch the agent installation file and follow the instructions. Accept the license agreement
2. In the Host name field, specify the IP address of the computer, where the agent is to be installed. In the Zabbix server IP/DNS field, specify the address of the Zabbix server, and enter the port it is listening to in the Agent listen port.
   We recommend checking the Add agent location to the PATH box so that it would be easier to check the agent operation via the console
   
3. Select the installation path and components, and then click Next and Install
   
   

As a result, the agent is installed and starts sending data to the server.

r_keeper 7 Settings

As part of the monitoring configuration, you should configure the r_keeper _ 7 INI files. It should be performed individually for each required module.

Open the INI file of the required server and add the following entries:

[ZABBIX]

...

; Zabbix server name / IP address (interface: Zabbix Trapper)

...

ZabbixAt = "172.22.10.152"

...

; Yhe own name at the Zabbix server: i.e. the name of the selected host (a single PC can have multiple modules with different names)

...

SelfName = "199995181-REP-01"

Add these settings for each required server.
Use examples:

1. Directories

   Reference server

   Code Block
   [ZABBIX]

...

1. ZabbixAt = "172.22.10.152"

...

1. SelfName = "199995181-REF-00"

   
   

2. Reports

   Report server

   Code Block
   [ZABBIX]

...

1. ZabbixAt = "172.22.10.152"

...

1. SelfName = "199995181-REP-01"

   
   

2. Cash server

   Code Block
   [ZABBIX]

...

1. ZabbixAt = "172.22.10.152"

...

1. SelfName = "199995181-MID-01"

   
   

2. Cash station

   Code Block
   [ZABBIX]

...

1. ZabbixAt = "172.22.10.152"

...

1. SelfName = "199995181-POS-01"

   
   

   Info
   If you need to run the service with a non-standard port, add the port with the "-p" key to the IP address in the INI files. For example: ZabbixAt = "192.168.15.15" "-p" "10055"

   
   Save INI files and restart the servers.

Zabbix

...

Settings

Template Import

...

Download the template file  right here , or from the attached filesfind it in the attachment.

Open the Zabbix web interface. By default, it is available hereat: http:// server IP-адрес сервера address/zabbix.

Log into the system.

• Login name — Admin
• Password — zabbix

Navigate to Configuration > Templates and click Import Import in the right corner. Template App R-Keeper 7 will appear on the list of templates.
Image Added

Select the uploaded file and click Import again.
 
It  It is recommended to delete unnecessary templates. For this purpose, set relevant flags and click Delete at the bottom.

Creating

...

Hosts

To create a host, first, you need to create a group. For this purpose, navigate to Configuration > Host Groups and click Create host group in the right corner  corner Image Added.
Specify the name of the new group and click Add
Image Added

Now, create the hosts.
Navigate to Configuration > Host and click Create host host.

Fill in the following fields:

• Host name — the name of the host. Only Latin letters without spaces are allowed. It should mandatorily must match the name specified in the server INI file .
• Visible name — the name to be displayed. It can contain spaces and Russian non-English letters.
• Groups — the group of hosts.
• Agent interfaces — the address of Zabbix agent address. Here, you should specify the r_keeper _ 7 IP address and port to be monitored.
• Other fields can be left empty.

Go to the "Templates" tab, click Add and select the newly installed Template App R-Keeper 7 from the list of templates. This action can be performed later in batch mode.
Image Added

Click Select. The template will be added to the host. Click Add in order to save the host settings.
Image Added

The host will appear on the list. Repeat the same actions for all required hosts.
 
Make  Make sure that a correct template has been selected for each host, otherwise, data will not be displayed.

Now, the configuration is complete, and you can proceed to monitoring.

Monitoring

Navigate to Monitoring > Latest data. Specify the group in the Host groups field and click Apply. In the list below, the monitoring data will appear. Currently, only the version transfer is available. In the future, the number of metrics there will be enhancedmore metrics.
If there is no data is contained in the columns Last check and Last value, it means that no data is received.

...

To check the transmission of data to the Zabbix server, use the manual launch of the zabbix_sender.exe console utility, which is installed together with the agent. This utility sends the given specified data to the server, and you can see it in the monitoring section.
Open the command line and launch the zabbix_sender utility:

C:\Program Files\Zabbix Agent\zabbix_sender.exe\zabbix_sender.exe -server_IP_address -s host_name -k metric-name -o metric_value

Key values:

• -z — IP address of the Zabbix server
• -s — host name
• -k — metric name
• -o — metric value

In case of a successful transmission, the following message appears: processed: 1; failed: 0. In case of errors, it will be vice versa.
Image Added

The transmitted metric value will appear on the monitoring page.

Metrics

...

Description

• rk7.app.version: version
  • Component version, f.ex.:
    • 7.6.4.212
    • 7.6.5.113
• Component version, e.g.:
• rk7.app.appkind: software type
  • Component type, f.ex.:
    • Reference
  • Directories
    • server ({A0AB2F9D-BC5A-4B6F-8E31-F08EF59E2A31})
    • Service station (POS) ({DA5D57BC-21C9-4DBD-B86F-F01B23B9862C})
• Component type, e.g.:
• rk7.app.netname: network name
  • Component network name within the r_keeper_7 infrastructure, f.ex.:
    • OA-02-MIDS-001
    • OA-02-CASH-001
• Component network name within the r_keeper_7 infrastructure, e.g.:

Attachments