Here are a few things to know when setting up data governance policies in the policy center:
What is the maximum number of assets that can be scoped to a policy?
There is currently no upper limit on the total number of assets that can be scoped to a policy. However, bear in mind that a higher asset volume can slow down the workflows for linking assets to the policy and completing compliance checks. It may also adversely impact the overall performance of Atlan, including search and discovery, workflow runtime, playbook execution, and more.
What is the maximum number of rules supported in a policy?
Atlan currently supports creating 10 rules per policy. However, as with a higher volume of assets, more rules can also slow down the completion of compliance checks. Note that checks for each rule run one at a time during the scanning process.
How many active policies can Atlan support?
There is no upper limit on the total number of active policies in Atlan. However, Atlan recommends that you proceed with caution. Multiple active or overlapping policies may delay the completion of compliance checks or adversely impact overall performance.
Can running playbooks on governed assets affect compliance checks?
Yes, compliance checks must operate in isolation from playbook runs. For any overlapping assets, compliance checks should not coincide with any ongoing or scheduled playbook runs. Failure to heed this warning may result in false incidents.
Can I use newly created metadata attributes to define the asset scope or compliance rules?
For any newly created glossary, category, term, tag, or custom metadata, you must wait a minimum of three hours before you can use them to define the asset scope or compliance rules in a policy.
For any changes to a linked asset that violate a rule, how long will it take to be reported as an incident?
The violation check operates in near real time. However, if there is a high volume of updates and the queue becomes congested, new updates will have to wait until existing ones have been processed.