Alation

Cloud data catalog building lineage from metadata extraction and query logs, with a policy centre.

Provider
default
Category
Data
Properties · 4 set by this component
propertytypevaluesrequiredkind defaultthis component
accessPolicyEnforcementboolean—no—▸ true
agentDeployment · component propertyboolean—nofalseinherited
classificationboolean—no—▸ true
columnLevelLineage · component propertyboolean—notrueinherited
connectorFramework · component propertyenumocf | nativenoocfinherited
lineageboolean—no—▸ true
managedboolean—nofalse▸ true
queryLogIngestion · component propertyboolean—nofalseinherited
scanScheduleenummanual | daily | weeklyno—inherited
sourceCountinteger—no—inherited
Rules that apply · 0

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

No rule reads this kind yet. That is a gap, not a guarantee.
Use it in a design
nodes:
  - { id: "alation", component: "alation" }
Other Data catalog products · 23
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# Alation: data catalog delivered as Alation Cloud Service.
# Alation docs: lineage is calculated from metadata extraction (MDE), query log ingestion (QLI)
# and Compose queries, both jobs run on a schedule against the source; the Policy Center manages
# and enforces access policies from one control point.
schemaVersion: "1"
type: "component"
id: "alation"
kind: "data-catalog"
provider: "default"
docs: "https://docs.alation.com/"
defaults:
  managed: true
  classification: true
  lineage: true
  accessPolicyEnforcement: true
properties:
  queryLogIngestion:
    type: "boolean"
    default: false
  columnLevelLineage:
    type: "boolean"
    default: true
  connectorFramework:
    type: "enum"
    values: ["ocf", "native"]
    default: "ocf"
  agentDeployment:
    type: "boolean"
    default: false

The same page as markdown, for an agent: /catalogue/components/alation.md