Load feedback resources

With load feedback, load balancing is controlled by measurements of entities, which you define, called resources. A resource is anything consumed by load on a data center, and is measured and reported to improve load balancing. As an example, for a database application, you might decide that the most important measurement of load is queries per second. For a static web server, you might choose to measure HTTP GET requests per second. A resource is just a name for something that you measure that reflects how you want to balance load across your data centers. You report the load in whatever units make sense to you. GTM considers loads as relative unit-less quantities.

When using load objects, it is critical that load information is generated in real time and scales in response to traffic. When GTM directs traffic to a data center for a given property, it expects to see the load value increase. If it doesn't, GTM will continue to send traffic there. Using load objects in an attempt to manually steer traffic will result in poor performance.

A resource constrains a property if it is affected or consumed by load on that property. A resource can be configured to constrain one or all properties.

Note: Resources can constrain multiple properties only if you are using XML load objects. With non-XML load objects, or with download score based load balancing, resources and properties are in a one-to-one relationship.

As an example, you may decide that you need to balance your use of Internet bandwidth. Since all Internet traffic consumes bandwidth, configure your bandwidth resource to constrain all of your properties.