Governance Action Framework (GAF)
The Governance Action Framework (GAF) provides the interfaces and base implementations for components (called Governance Action Services) that take action to:
- detect, report and eventually correct a situation that is harmful to the data or the organization in some way or
- to enhance the metadata to improve its use.
The Governance Action Framework can be used for three purposes:
- Provide the complete implementation and orchestration of a governance process.
- Provide coordination between processes run by specialized governance systems. For example, coordinating a DevOps pipeline with a data movement and quality process and security incident management.
- Provide contextual metadata plus an audit trail of actions managed by an external governance process.
Governance Action Services
There are five types of Governance Action Services:
Watchdog Governance Service - monitors for specific types of instances, or changes to open metadata and initiates appropriate follow on governance actions either by creating a governance action, a governance action process or an incident report. For example, a watchdog service may detect a new asset and kick off an asset onboarding governance action process.
Verification Governance Service - performs a series of tests around a specific metadata instance.
Triage Governance Service - evaluates a reported situation and makes a choice on the right action to proceed. This may involve a human decision maker.
Remediation Governance Service - performs a change to the open metadata (or its counterpart in the real-world).
Provisioning Governance Service - performs an action that makes a new resource available along with the appropriate open metadata.
Collectively they are called the Governance Services.
Each type of service supports a specialist governance activity. The governance action services are linked together into
Some governance action services invoke functions in external engines that are working with data and related assets. The GAF offers embeddable functions and APIs to simplify the implementation of governance action services, and their integration into the broader digital landscape, whilst being resilient and with good performance.
Implementing governance action services
Governance action services are open connectors (see Open Connector Framework (OCF)) that support the interfaces defined by the GAF. They may produce audit log records and exceptions and they may make changes to metadata through the Open Metadata Access Services (OMASs).
Configuring the governance action services in open metadata
Running governance action services
Governance action engines are hosted by Open Metadata Engine Services (OMES). There is a specific engine service for each type of governance action engine defined in the open metadata.
- Asset Analysis OMES - supports Open Discovery Engines from the ODF.
- Metadata Watchdog OMES - supports the Open Watchdog Engine.
- Request Triage OMES - supports this Open Triage Engine.
- Issue Remediation OMES - supports the Open Remediation Engine.
- Action Scheduler OMES - supports the Open Scheduling Engine.
- Asset Provisioning OMES - supports the Open Provisioning Engine.
The engine services run in dedicated OMAG Server called the Engine Host. Instructions for configuring the engine services in the Engine Host are found in the Administration Guide.
Return to frameworks.
License: CC BY 4.0, Copyright Contributors to the ODPi Egeria project.