> For the complete documentation index, see [llms.txt](https://docs.pharos.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/accessing-logs/list-views.md).

# List Views

Understand the logs tab, default list views, and custom list views you can build.

## The Logs Tab

The Logs tab serves as your primary entry point for working with individual error records in Pharos. Like any other object tab in Salesforce, it displays your log records in a familiar list format with columns showing key information at a glance. Since logs are stored as standard Salesforce custom objects, navigating and interacting with them follows the same patterns you use throughout the platform.

When you access the Logs tab, you'll find a collection of pre-configured list views designed to help you quickly filter and organize error data. These default views provide common filtering patterns that address typical troubleshooting scenarios, but they're just a starting point. The real power comes from creating custom list views tailored to your specific organizational structure and workflow needs.

## The Issues Tab

While the Logs tab provides access to individual error records, the Issues tab offers a higher-level view that aggregates related logs together. This aggregation transforms thousands of individual log entries into a manageable set of distinct problems, making it far easier to understand the overall health of your system and prioritize remediation efforts.

An Issue represents a cluster of identical or nearly-identical errors, grouped together through Pharos's fingerprinting algorithm. When the same flow fails repeatedly, or an Apex class throws the same exception across multiple users, all those individual log records roll up into a single Issue record. Instead of seeing 500 separate logs for the same problem, you see one Issue with a log count of 500. This consolidation dramatically reduces noise and helps you focus on unique problems rather than repetitive occurrences.

The Issues tab becomes particularly valuable when managing production systems with high transaction volumes. Rather than scrolling through endless individual error records trying to identify patterns, you can immediately see distinct problems, their frequency, their impact on users and data, and their resolution status. Each Issue provides aggregate metrics like total occurrences, unique affected users, average frequency, and trends over time—information that would require manual analysis if working with individual logs.

For day-to-day operations, many teams find themselves working primarily with the Issues tab for monitoring and triage, only diving into the Logs tab when they need to examine specific error contexts or debug details. The Issues tab answers questions like "What problems do we have?" and "Which ones matter most?" while the Logs tab answers "What exactly happened in this specific instance?"

Like the Logs tab, the Issues tab supports both default and custom list views, allowing you to filter Issues by category, functional area, status, priority, or any other field on the Issue record. You might create an "Open High-Priority Issues" view for daily standup reviews, a "My Team's Issues" view filtered by functional area, or a "Recent Issues" view to monitor newly discovered problems.

The relationship between logs and Issues is foundational to effective use of Pharos. Every log belongs to exactly one Issue, and every Issue contains one or more logs. Understanding when to work at the Issue level versus the log level helps you operate more efficiently—use Issues for the big picture and prioritization, use logs for detailed investigation and debugging.

→ [Learn more about how Issues are created and managed](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker.md)

## Default List Views

Pharos ships with a single default "All" list view on both the Logs tab and the Issues tab, giving you an unfiltered look at every record so you have somewhere to start immediately. From there, the real power comes from building your own custom list views tailored to how your team actually triages work.

Most teams quickly move beyond the default view and create additional custom views—filtered by category, functional area, time range, or any other field that matches their specific needs. The sections below walk through common patterns for building those views.

## Creating Custom List Views

Custom list views allow you to filter log data based on any field available on the log record. This flexibility enables you to create views that match your organizational structure, technical architecture, and operational processes. The process of creating a custom list view for logs works exactly like creating one for any other Salesforce object—you define filter criteria, select which columns to display, choose a sort order, and save the view for yourself or share it with your team.

### Filtering by Functional Area

One of the most powerful approaches involves filtering logs by functional area. If your organization uses naming conventions or metadata to identify which team or product area owns specific automations, you can create list views that show only the logs relevant to each team. For example, a "Sales Automation Errors" view might filter for logs where the functional area contains "Sales" or where the flow API name starts with a specific prefix. This allows each team to focus on their own errors without wading through unrelated issues.

### Category-Based Views

Many teams find value in creating views organized by technical category. You might create separate views for Flow errors, Apex exceptions, bulk API failures, and integration issues. This segmentation helps route problems to team members with the appropriate technical expertise. A flow specialist can focus on the Flow errors view, while developers concentrate on Apex exceptions.

### Time-Sensitive Views

Creating views based on specific time ranges helps with different operational needs. A "Today's Errors" view provides a real-time snapshot of current issues, useful during hypercare periods or after deployments. A "This Week" view offers slightly broader context for weekly triaging sessions. You might also create views for specific dates around release windows to monitor the impact of deployments.

### Business-Critical Views

Some errors deserve special attention because they affect critical business processes. You can create views that filter for specific flows, Apex classes, or operations that handle essential functionality like order processing, customer onboarding, or financial transactions. Adding criteria based on fields like impacted user count or frequency helps surface the issues that demand immediate attention.

## Field Selection and Column Configuration

Beyond filtering criteria, custom list views let you choose which fields appear as columns and in what order. This customization ensures you see the most relevant information without excessive scrolling or clicking into individual records. Common columns include the error summary, category, type, functional area, running user, creation date, and associated issue. Some teams add custom fields specific to their implementation, such as business process identifiers or severity indicators.

## Sharing and Visibility

List views can be private (visible only to you), shared with specific groups, or made public to all users. As you develop useful views, consider sharing them with teammates who would benefit from the same filtering logic. This sharing promotes consistency in how your team approaches log analysis and reduces duplicate effort.

## Using List Views in Daily Operations

List views become part of your daily workflow for monitoring and responding to errors. During routine checks, you might scan through your "Today's Errors" view to spot any emerging issues. When triaging problems, you might work through a specific functional area view to batch similar issues together. After a deployment, you might create a temporary view filtered to a specific time range to isolate any new problems introduced by your changes.

The combination of default and custom list views provides flexible access to your log data, ensuring that whether you're troubleshooting a specific issue or performing routine monitoring, you can quickly find the relevant information without getting overwhelmed by volume.
