Project

General

Profile

Actions
Copy link

Enhancement #472

closed

Rework Zabbix Architecture

Added by Marc Dequènes over 8 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Marc Dequènes
Category:
Service :: Supervision
Start date:
2015-08-02
Due date:
% Done:

100%

Estimated time:
Patch Available:
Confirmed:
No
Branch:
Entity:
DuckCorp
Security:
Help Needed:

Description

In order to improve efficiency and reduce load on the server, we should have a look at:
  • using a proxy (to poll the outside, and later when the server move to poll the inside)
  • experimenting with active checks (can it be used to properly bundle and efficiently send back measurements instead of polling for each petty item?)
Actions
Copy link
 #1

Updated by Marc Dequènes over 8 years ago

  • Status changed from New to In Progress

A few days ago i installed a proxy on Elwing and worked on the related Ansible rules.
I had to fix the extra MIBs installation.
I also had to ensure the source IP is OK (netfilter rule affecting all traffic originating from Elwing himself).

Actions
Copy link
 #2

Updated by Marc Dequènes over 8 years ago

  • % Done changed from 0 to 20

Today I adapted the systemd template to be fully active in order to have a look at the load and queue evolution, as clearly these frequent measurements have an important impact.
I had to adapt the firewall rules in order to protect the Zabbix trapper port, as Zabbix does not provide any authentication.

Actions
Copy link
 #3

Updated by Marc Dequènes over 8 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 20 to 100

Adapted config because the Zabbix server moved to Korutopi, so the proxy on Elwing is now reversed.

Also adapted the active server setting in the agents configuration to take care of the specific port number on Korutopi.

Actions
Copy link

Also available in: Atom PDF