Configure ECG for AutoStopping Rules
This topic describes how to configure ECG for AutoStopping Rules. You can assume ECG as an event emitter for your rule. It sends usage records for the configured rules.
When the ECG is configured to watch a workload, an AutoStopping Rule will not stop the resource until the workload finishes running. ECG comes with the following pre-installed watchers:
- Metrics
- Process
By default, the AutoStopping Rule listens to HTTP/HTTPS traffic. On the other hand, a resource can be working on long-running background jobs like batch jobs. Nightly data updates or scheduled processing, for example. In this scenario, relying just on network traffic to detect resource idleness is not the ideal solution. For such scenarios, you can configure ECG for your AutoStopping Rules.