Raising Governor Limits and Audit Logs

Rego adheres to the default Governors and Limiters built into the standard Clarity environment.  Rego has confirmed that raising these limits can causes issues such as system instability, outages, or performance degradation.  As such, Rego recommends breaking apart queries or reports that are hitting a limit so that you can pull the data incrementally.  It is also recommended to develop a Data Extractor to return large data sets.  Certain activities may require elevated audit logging, which also contributes to performance degradation. Audit logs may occasionally be temporarily raised for troubleshooting purposes only.

In rare cases, Rego will raise the Governors.  This requires approval from Rego’s leadership.  In order for them to make the decision to raise the Governors, the following information must be provided (Document Below):

1. A comprehensive business case must be defined.  This needs to include the reason for the raise, why the other methods will not work and what the limit would need to be raised to.

2. A Testing Plan and acknowledgement of downstream impacts.

3. Acknowledgement that this will void SLAs for uptime as the change is known to cause system instability, degradation, and outages.

4. Approval from Contract Owner and at least one Jira Approver.

Please note that this does not guarantee a raise in the Governors unless also approved by Rego.

Exceptions Case Document:

Open