Ad Widget

Collapse

Separating Frontend

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • emz
    Junior Member
    • Mar 2014
    • 20

    #1

    Separating Frontend

    Hello,

    I am currently running a Zabbix environment consisting of a Zabbix Server (both collecting data and hosting the web interface), a separate server for DB and one proxy.

    There are constantly opened sessions to the Web interface and that generates some network traffic that I wish to avoid. My idea - to install a new server that would only be responsible for hosting the Web interface (along with the server that collects data). So, the web view would be visible on both servers - the main Zabbix Server and on a "console server".

    Is that possible?
    Will the setup be efficient?
    Would the Web frontend generate too much traffic to read the data from the database?

    I use Zabbix v3.0.8.
  • toine7m
    Member
    • Feb 2017
    • 93

    #2
    I'm currently on a project a bit different than yours, but I can tell you that the traffic will be huge between the servers :/

    You can use grafana or something else if you want to use your frontend in another server, but in other ways , imo, it'll generate too much traffic

    Comment

    • emz
      Junior Member
      • Mar 2014
      • 20

      #3
      Yes, you are probably right but there should be some way to mitigate the traffic. Because if there are 10 and more constant connections to the Web interface the network load could be an issue.

      Any way to compress the traffic?

      Comment

      Working...