Extraction and Discovery Intervals

Customize how often Veza updates your Authorization Graph

Veza periodically connects to integrated systems to maintain an up-to-date graph of authorization and relationships between entities in your environment. This process involves two main activities: discovering new data sources and extracting authorization metadata.

Understanding Intervals

Discovery Interval

  • Determines how often Veza checks for newly added data sources in your integrated systems.

  • The discovery interval can be set between 15 minutes and 30 days.

Extraction Interval

  • Determines how often Veza collects authorization metadata to update entities in the Authorization Graph.

  • Extraction intervals can be set between 1 hour and 30 days.

  • Gathers supported entities and their attributes, which can take some time for large data sources.

Benefits of Customizing Intervals

  • Cost Reduction: Longer extraction intervals can reduce compute costs for systems like Snowflake, where each extraction may incur API charges.

  • Performance Improvement: Increasing intervals for integrations with large data sources can prevent bottlenecks and reduce delays in updating other integrations and services.

How to Customize Intervals

  1. Open the System Settings page on the main Veza navigation bar.

  2. Locate the Pipeline section.

  3. Use the dropdown menus to set global values for discovery and extraction intervals.

  4. To customize intervals for specific providers:

    • Use the Search field to filter the list of providers.

    • Set custom values for individual providers as needed.

    • Note that any active overrides for each provider will appear at the top of the list.

Considerations

Tuning extraction and discovery intervals can optimize performance while maintaining an up-to-date view of your authorization landscape.

  • Balance frequency of updates with system performance and cost.

  • Monitor the impact of your changes to ensure they meet your organization's needs.

  • Remember that less frequent updates may result in slightly outdated data between extractions.

Last updated