Web Aplications monitoring best practice

[paulo.soares]

Hello!

We have various web applications monitored by Zabbix web scenarios. Everything works fine, but when some application goes down, we can't only search on Zabbix for that application, because it is only one from various web scenarios added on a single host.

I wonder if i can register that applications as hosts, without any item or template, only the web scenario and a simple trigger to alert when the scenarios goes down. I wonder too if that would be a good idea..

I'm new on Zabbix forum, so, sorry if i placed my question on the wrong place.

Thanks for all help!

[timbo]

Hi paulo.soares,

Forgive me if I have misread your question, but hosts are simply containers for items (and web checks) and don't need to be associated with a computer/device.

While it is easiest to think of Hosts being linked to a physical device, they are far more flexible than that. We have Hosts that are named after distributed software applications that run over multiple physical servers. This allows us to monitor the general health of the application. We then monitor each physical server as a separate host to ensure they're operating as expected.

So if I'm reading your question correctly, I'd suggest that you start making more hosts (just leave the "Agent interfaces" as 127.0.0.1 or 0.0.0.0 - nothing will be sent to those addresses unless you add Agent Items to the host).

Perhaps you could split all out web checks onto their own host:
Host: Web App 1 (contains: Web Check 1)
Host: Web App 2 (contains: Web Check 2)
Host: Web App 3 (contains: Web Check 3)

Then any triggers fired would be on the appropriate host.

I hope that helps!

-Timbo

[paulo.soares]

Thanks

Hello Timbo!

I was stuck on the definition of Host=Physical Device, and wondering if will be a good idea break that definition.

But like you said, "(hosts) are far more flexible than that". I'll give a try.

Thanks!