HTTP/S Template Node Assignment Best Practices

hpstech

I have applied all of our different HTTP/S components and associated templates to point at our main polling engine.

What is the best practice when applying a template with HTTP/S components?

Since the template contains URLs for many different servers, I've applied these historically to one server, the MPE.

Now that we have enabled HA, how will these templates react during a manual HA fail-over? Will a MPE in failed over state continue to poll these templates?

Do you guys (or girls) apply HTTP/S template directly at the server with the associated URL?

A dedicated Agent?

A polling engine? Or other?

What is the best practice for applying HTTP/S monitors to a specific node? What Node do you choose?

mesverrum

So for several reasons I prefer to monitor http/s templates by applying them to the node that hosts the page directly. If there's a load balanced VIP or DNS name then I usually make a separate node for that object as well, unless the client has license limits we need to stay under. In some cases I mute or otherwise hide alerts from the individual pool members and only trigger on the VIP/dns entry so my stats reflect the end user experience, but I can still report on the stats for each individual pool member if needed down the line.

Mostly for me it has to do with having the SAM template show up as a related object to the node and for some cascading custom property stuff I usually do where sam apps inherit properties from the node they are associated with. 

In smaller environments I can appreciate the model where you just stick all the monitors on a big template and attach them wherever because if you are hard coding the url in then it doesn't actually matter what node you associate them with, but I like documenting my relationships as accurately as possible if I can.