Pulse

Pulse can monitor a service on a regular (five minute) interval, or be invoked by a service as it is used.

It's designed to monitor external, third party services, and elements in the Platform that integrate with them.

Pulse shouldn't be used to monitor standard Platform components, like subsites or API Server workers. That's because Pulse is built on and in the GOSS Platform, so monitoring an API Server worker like History, or the iCM API, doesn't make sense because Pulse itself uses those services.

Pulse calculates a state for each service it monitors, which will help you answer:

• Is it healthy or down?
• Is it degraded (slow)?
• How many failures have we had in a row? (if down)
• What's the average latency across the last 100 (or configured) events?
• What's the 95 percentile of response times across the last 100 (or configured) events?