> ## Documentation Index
> Fetch the complete documentation index at: https://support.entegrata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Collection Settings

> Configure connection-level schedules, throttling, and collection behavior

## Overview

Connection collection settings define default behavior for all resources within a connection. Individual resources can override these defaults with their own settings.

<Info>
  Collection settings apply to all resources in the connection unless overridden at the resource level.
</Info>

## Accessing Collection Settings

<Steps>
  <Step title="Navigate to Connection">
    Click on a connection to view its Resources page
  </Step>

  <Step title="Open Settings">
    Click the **Settings** icon (gear) in the Collection section
  </Step>

  <Step title="Configure in Modal">
    The Collection Settings modal opens
  </Step>
</Steps>

## Schedule Configuration

Choose how and when resources in this connection collect data.

### Interval-Based Scheduling

Resources collect on regular time intervals or at specific times.

**Options**:

* Specific times: "Daily at 2:00 AM", "Weekly on Sunday at 3:00 PM"
* Regular intervals: "Every 6 hours", "Every 30 minutes"

<Tip>
  Use interval scheduling for most use cases - it's simple and reliable.
</Tip>

### Timing: Static vs Rolling

For schedules that run **more than once a day** (for example every 2 hours or every 30 minutes), you can choose how each run is timed:

<Tabs>
  <Tab title="Rolling (default)">
    The next collection is scheduled for one full interval **after the previous one finishes**. This is simple and reliable, but the exact run time drifts depending on how long each collection takes.

    *Example*: an "every 2 hours" collection that starts at 1:00 and takes 5 minutes finishes at 1:05. The next run is scheduled 2 hours **after it finished** — so it starts at 3:05 (not 3:00), finishes at 3:10, and the following run starts at 5:10, and so on. Each run drifts a little later by however long the previous one took.
  </Tab>

  <Tab title="Static">
    Collections run on a **fixed clock schedule** anchored to a **start time** you choose, regardless of how long each run takes.

    *Example*: "every 2 hours" with a start time of 6:15 always runs at 6:15, 8:15, 10:15, … — on the dot.
  </Tab>
</Tabs>

When you choose **Static**, set a **Start time** — the time of day the schedule is anchored to, shown in your instance's timezone. Daylight saving is handled automatically, so runs stay at the same local time year-round.

<Note>
  The Timing option only appears for sub-daily schedules (hourly or minute-level intervals). Schedules that run daily or less often already fire at a specific time of day, so there is nothing to anchor.
</Note>

<Tip>
  Choose **Static** when you need predictable, evenly-spaced runs (for example "every 2 hours on the dot"). **Rolling** is fine for most cases.
</Tip>

## Collection Profile

Control collection speed to manage load on your source systems.

Information can be found in the [Throttle Profile](/data/collector/connections/overview#throttle-profile) documentation.

<Note>
  Profile settings affect API rate limiting and database query batching but don't change schedules.
</Note>

## Active Status

Enable or disable collection for the entire connection.

**Active** (Toggle ON):

* Resources collect according to their schedules
* Discovery runs automatically every 3 hours
* Normal operation

**Inactive** (Toggle OFF):

* All data collection paused
* Discovery still runs but no data is collected
* Use for temporary suspension (e.g., maintenance windows)

<Warning>
  Setting a connection to Inactive stops ALL resource collection, even if individual resources are enabled.
</Warning>

## Saving Settings

After making changes:

<Steps>
  <Step title="Review Changes">
    Verify all settings are correct
  </Step>

  <Step title="Click Save">
    Click the **Save** button at the bottom of the modal
  </Step>

  <Step title="Confirm Application">
    Settings apply immediately to the connection and all resources using defaults
  </Step>
</Steps>

## How Settings Apply to Resources

### Default Behavior

Resources without their own collection settings inherit from the connection:

| Connection Setting | Applies to Resources                             |
| ------------------ | ------------------------------------------------ |
| Schedule           | Resources with no custom schedule                |
| Active Status      | All resources (connection inactive = all paused) |
| Collection Profile | All resources unless overridden                  |

### Resource Overrides

Individual resources can override:

* ✅ Schedule (intervals)
* ✅ Active status (if connection is active)
* ❌ Collection profile (always inherits from connection)

<Info>
  See [Resource Collection Settings](/data/collector/resources/collection-settings) to configure resource-specific overrides.
</Info>

## Best Practices

<CardGroup cols={2}>
  <Card title="Start with Interval Scheduling" icon="clock">
    Use simple interval schedules until you need more complex scheduling
  </Card>

  <Card title="Schedule During Off-Peak Hours" icon="moon">
    Set collection times when your source systems have low activity
  </Card>

  <Card title="Use Standard Profile First" icon="gauge">
    Only change to High or Low if you have specific performance needs
  </Card>

  <Card title="Test Schedule Changes" icon="flask">
    Monitor the first few collections after changing schedules to verify timing
  </Card>
</CardGroup>

## Common Scenarios

### Scenario: Daily Overnight Collection

**Goal**: Collect all connection data once per day at 2:00 AM

**Configuration**:

* Schedule Type: Interval
* Schedule: "Daily at 2:00 AM"
* Profile: Standard
* Active: ON

### Scenario: Frequent Real-Time Updates

**Goal**: Keep data as current as possible with hourly updates

**Configuration**:

* Schedule Type: Interval
* Schedule: "Every 1 hour"
* Profile: High (for maximum speed)
* Active: ON

### Scenario: Maintenance Window

**Goal**: Temporarily pause collection during source system maintenance

**Configuration**:

* Active: OFF
* (Keep all other settings unchanged)
* Re-enable Active when maintenance completes

## Troubleshooting

### Settings Not Applying

**Symptoms**: Changes saved but collection behavior doesn't change

**Possible causes**:

* Resources have overriding settings
* Connection is inactive
* Schedule hasn't triggered yet

**Resolution**:

1. Check individual resource settings for overrides
2. Verify connection Active status is ON
3. Wait for next scheduled time or trigger manual collection

###

<CardGroup cols={2}>
  <Card title="Resource Collection Settings" icon="table" href="/data/collector/resources/collection-settings">
    Override connection defaults for specific resources
  </Card>

  <Card title="Monitoring Jobs" icon="chart-line" href="/data/collector/jobs/overview">
    Track collection execution and verify schedules
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/data/collector/connections/troubleshooting">
    Resolve collection issues
  </Card>
</CardGroup>