search

sni / Thruk

Thruk is a multibackend monitoring webinterface for Naemon, Nagios, Icinga and Shinken using the Livestatus API.
http://www.thruk.org
Other
408 stars 148 forks source link

Backend behind proxy #906

Closed jevvz closed 5 years ago

jevvz commented 5 years ago

This isn't a bug. It's a question about the settings selecting http as backend.

In the backend configuration for http there is a proxy parameter. Is this parameter valid in a scenario where you have a Thruk site behind the corporate network?

The Thruk site behind the corporate network isn't reachable from inside the corporate network. Want to know if it would be reachable putting in the settings a proxy. And if this could be done beside the destination, ports 80 and 443 need to be allowed in the proxy, are there more ports who need to be allowed?

What about the queries to the REST API from the hosts and services in the Thruk site behind the corporate network? Are the http setting valid also for the REST API?

Thanks in advance.

Jorge.

sni commented 5 years ago

The proxy option simply enables using a proxy solely for the connection from the central thruk to the backend thruk. So if your setup looks like [central thruk] -> http -> [backend thruk] -> livestatus -> [naemon] then enabling the proxy would simply change that to: [central thruk] -> http over proxy -> [backend thruk] -> livestatus -> [naemon]