What is a Time Interval Configuration?
Your users are querying 2 years of logs when they only need the last 7 days. Searches are slow, compliance is at risk, and your support team gets calls they shouldn't need to handle.
A Time Interval Configuration solves this. It bundles one or more Time Intervals into a named policy—"Last 7 days", "Last 30 days", "Last 90 days"—and attaches that policy to a Log View. Users can only search within the allowed window.
The result: fast, governed, role-appropriate data access—without anyone calling an admin.
How It Fits Together
A Time Interval Configuration sits between your raw Time Intervals and your Log Views:
7-day window"] TIC2["fa:fa-chess-clock Support Team
30-day window"] TIC3["fa:fa-chess-clock Auditors
90-day window"] LV1["fa:fa-table-list Order Status Log View"] LV2["fa:fa-table-list Production Error Log View"] LV3["fa:fa-scale-balanced Compliance Log View"] TI1 --> TIC1 TI2 --> TIC2 TI3 --> TIC3 TI2 --> TIC2 TIC1 -.->|restricts| LV1 TIC2 -.->|restricts| LV2 TIC3 -.->|restricts| LV3 style TIC1 fill:#fff3e0,stroke:#f57c00,stroke-width:2px style TIC2 fill:#fff3e0,stroke:#f57c00,stroke-width:2px style TIC3 fill:#fff3e0,stroke:#f57c00,stroke-width:2px style LV1 fill:#e8f5e9,stroke:#388e3c,stroke-width:2px style LV2 fill:#e8f5e9,stroke:#388e3c,stroke-width:2px style LV3 fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
Reusable Time Intervals feed into named configurations, which restrict what users can search in each Log View.
What It Is
A Time Interval Configuration is a named collection of Time Intervals that defines the allowed search windows for a Log View.
Info
Example: A configuration named "Support Team Access" contains three options: "Last 24 hours", "Last 7 days", "Last 30 days". When it is assigned to a Log View, users can pick one of those windows—nothing older is accessible.
| Property | Description | Example |
|---|---|---|
| Name | A descriptive label for the policy | GDPR - 90 Day Limit |
| Time Intervals | One or more Time Intervals the user can choose from | 7 days, 30 days, 90 days |
When to Use It
Assign a Time Interval Configuration to a Log View when that view is:
- Accessed by business users who need quick, relevant results without wading through years of history
- Subject to compliance rules (GDPR, HIPAA, SOX) that mandate access limits
- Experiencing performance issues from unbounded date range queries
- Shared by roles with different data retention needs
Why It Matters
| Situation | Without Configuration | With Time Interval Configuration |
|---|---|---|
| Performance | Users search 3 years of data, queries time out | Limited to 30 days—queries are fast |
| Compliance | Personal data is freely accessible indefinitely | Access beyond 90 days is blocked |
| Self-service | Business users call support to find today's orders | They select "Last 24 hours" from a dropdown |
| Role-based access | Everyone sees the same unbounded window | Auditors get 90 days, business users get 7 days |
Real-World Example
Scenario: An order management team uses a Log View to check today's orders. Without a restriction, analysts accidentally search 6 months back—slow queries, irrelevant results, compliance risk.
Solution:
- Create Time Intervals: "Last 24 hours", "Last 7 days", "Last 30 days"
- Create a Time Interval Configuration: "Order Team Access" using those three intervals
- Assign "Order Team Access" to the "Order Status" Log View
Result: Analysts see a dropdown with three sensible options. Queries run in seconds. No data older than 30 days is ever accessible from that view.
An example of a Time Interval Configuration in use within a Log View.
Next Step
Add or manage a Time Interval Configuration
Related Topics
Time Interval — The individual time definitions used inside configurations
Log Views — Where Time Interval Configurations are assigned
Access Management — Control who can see what with role-based access