...
This script is taken from Installing on Debian and Ubuntu — RabbitMQ and may need an update in future. Even better option would be to provide erlang and rabbit packages and install from them.
2) You may verify the installation is working by opening http://your.host:15672
...
- Default Monitoring API IP: The default IP to be used for API calls (heartbeat, activation, etc.) for managed server monitoring, as multiple IPs may be available depending on the Provision set up. This is the IP of ProVision's server, at which the managed servers will send API requests. This is because if systemd-resolved is stopped, it is highly possible that ProVision's host is not resolvable. For this reason we make the API requests similar to "curl https://194.24.189.120/api/endpoint -H 'provision.mycompany.com'". Here, we list the local IPs of ProVision.
- Note: The Default Monitoring API IP can be set to a default value in this area, but it may also be set individually per managed server as an override.
- Verify CA: Toggle to "on" if you wish to enable the CA check.
- Communication type: Push (when the server pushes data to ProVision) and pull (when ProVision connects to the server and pulls the data). Push is preferred, but Pull-based may be desirable in cases where a firewall would not allow inbound connections to ProVision.
- Monitoring of the system: Toggle to "on" to enable monitoring of system statistics.
- System monitoring interval: How often (in seconds) the system will be checked. The smaller the interval, the more data there will be to store.
- Monitoring of the DNS: Toggle to "on" to enable gathering statistics from the DNS server.
- DNS monitoring interval: How often (in seconds) the DNS server will be monitored. Data will be aggregated for the set period of time and the aggregated results will be sent.
- Raw data retention: The number of minutes to retain raw data. By default, this is set to 1440 minutes (1 day). Raw data requires sizable storage needs.
- Aggregated data retention: The number of days to retain aggregated data.
...
Fill in the remaining update settings as applicable to the selected update mode:
- Internet Docker Update (recommendedRecommended) - This uses a Docker update directly from our docker registry. Internet connection is required for the managed server in order this mode to work. When this is chosen fields to enter tokens for our gitlab/registry appear to be filled in:
...
| Expand | |||
|---|---|---|---|
| |||
Update Settings - Docker Update Mode (Internet)
API timeout: Timeout for API calls in milliseconds. Update Mode: Enter the source for updates, depending on internet accessibility. Two options are available:
Test Tokens: Click to test the applied tokens for DNS, DHCP, and Monitor. 4 |
ProVision Image Download - This is for updates from ProVision. No internet connection is required from the managed server.
When this option is selected you have to get the image files from our gitlab and upload it in ProVision. The relevant gitlab project is at https://git-lju.6connect.com/6connect/pv-monitor/-/releases
| Expand | |||
|---|---|---|---|
| |||
| Expand | |||
| |||
Update Settings - Image Download (Local)If Update Mode is set to "Image Download (Local)", then the following settings will display:
Image file: Attach the Image file for upload to ProVision. API timeout: Timeout for API calls in milliseconds. Update Mode: Enter the source for updates - Image Download (Local), or opt to change to Docker Update (Requires Internet).
Images history: Available only after saving changes. Test Tokens: Click to test the applied tokens for DNS, DHCP, and Monitor. |
...