Why Use Views?
Instead of rebuilding the same filter combinations every time production breaks, save them as views and access them with one click.Save Time
No more rebuilding the same filters every incident
Quick Switching
Switch between different monitoring scenarios instantly
Stay Organized
Keep your most important queries organized
Share with Team
Soon
Team members can access shared views
Creating a View
Name It
Give your view a descriptive name like “Production API Errors” or “Staging Deployment Logs”.
Best Practices
Create Views for Common Scenarios
Create Views for Common Scenarios
Think about the log queries you run most often and save them as views. Production errors, staging logs, specific services - if you check it regularly, make it a view.
Use Descriptive Names
Use Descriptive Names
Name views based on what you’re investigating, not just the filters. “API Gateway Timeouts” is better than “Production Errors”.