add monitoring

[evgeni]

No description provided.

[ekohl]

I wonder if we should not expose this as a parameter but instead set zabbix::agent::server via Hiera. Then we can simply include profiles::monitoring::client in our base profile. Or even just include zabbix::agent in profiles::base.

If we then include profiles::monitoring::server before profiles::base the explicit server for the agent should work.

[evgeni]

Architectural question.

Zabbix can run passive agents (Server connects to Agent) and active agents (Agent connects to Server).
You have to configure each monitored system to be either passive or active (meh), as it slightly changes how data is transmitted (and requires you to use different templates 🙄).

The question is, which one do we want?

• Active has the benefit that we only need one open port: the one for Zabbix on the monitoring box
• Passive means that the Server needs to be able to connect to each agent, either via v6 or v4 (we have boxen with "only" for each of those) and thus needs to be dual-stacked (eliminating quite a few hosting locations).

With these in mind, I think I'd aim at an active setup?

[ekohl]

I would also lean to an active setup.

Another question is where we want to host this. I was leaning to Netways since we have few hosts there so there's a good chance you'll find connectivity issues, but we don't have IPv6 there.

[evgeni]

Another question is where we want to host this. I was leaning to Netways since we have few hosts there so there's a good chance you'll find connectivity issues, but we don't have IPv6 there.

That should be fine as long as our v6 agents have v4 NAT or something.

[ekohl]

I'd also like to monitor HTTP remotely. Mostly for Jenkins & Discourse. If we have IPv6 we can also ensure Jenkins & Foreman are available over that.