Skip to content

Views Best Practices

Naming Conventions

Use clear, descriptive names that indicate:

  • Purpose: What the View monitors
  • Scope: What data it includes
  • Context: When or why it's used

Examples:

  • "Critical PI Server Errors - Production"
  • "Hourly Asset Health Check"
  • "Compliance Review - Q4 2024"

Organization Tips

  • Create Views for Regular Tasks: Save filters you use weekly or daily
  • Share Team-Critical Views: Make important monitoring Views available to your team
  • Use Descriptions: Add context about when and why to use each View
  • Regular Cleanup: Remove outdated Views to keep your list manageable

Alert Strategy

  • Start Conservative: Begin with higher thresholds and adjust based on actual patterns
  • Use Cooldowns: Prevent alert spam by setting appropriate cooldown periods
  • Test First: Verify your alert conditions work as expected before enabling
  • Document Purpose: Use descriptions to explain why alerts are configured

Troubleshooting

View Not Loading

  • Verify you have access to the original data source
  • Check if underlying filters reference deleted or renamed assets
  • Ensure your domain permissions haven't changed

Alerts Not Triggering

  • Confirm alert threshold and operator settings
  • Check that the cooldown period has elapsed
  • Verify the View returns data when accessed manually

Sharing Issues

  • Ensure recipients are in the same domain
  • Check that shared Views aren't using private data sources
  • Verify domain sharing permissions are enabled

Integration with Workflows

Views can be connected to automated workflows for advanced automation:

  • Incident Response: Trigger workflows when critical thresholds are exceeded
  • Reporting: Generate reports when specific conditions are met
  • Notifications: Send custom alerts through various channels
  • Remediation: Automatically attempt to resolve detected issues

Connect workflows through the alert configuration interface by selecting from available workflows in your domain.