> 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/reports-and-dashboards.md).

# Reports and Dashboards

Learn about the built-in homepage dashboard and how to build custom reports.

## Visual Insights Into System Health

While list views excel at providing filterable access to individual log records, reports and dashboards offer a different perspective—one focused on trends, patterns, and visual analysis over time. Pharos includes a comprehensive homepage dashboard that surfaces key metrics and charts immediately upon accessing the application. These pre-built visualizations provide instant visibility into error volumes, issue types, resolution status, and impact across your Salesforce environment.

The homepage dashboard serves multiple purposes. It acts as a daily health check for teams monitoring system stability. It highlights emerging problems through trend analysis. It provides executive-level visibility into observability metrics. And it demonstrates the kinds of insights you can derive from log data, inspiring ideas for custom reports and dashboards tailored to your specific needs.

## The Homepage Dashboard

The Pharos homepage dashboard presents a curated collection of charts and metrics designed to answer common questions about system health and error patterns. Rather than providing a single monolithic view, Pharos organizes dashboard capabilities into three primary functional areas, each serving distinct operational needs: operational health tracking through the Issues Dashboard, real-time incident response through the Triage Dashboard, and technical analysis through the Automation Dashboard.

### The Issues Dashboard: Operational Health

The Issues Dashboard provides a high-level retrospective view of system stability and error trends over time. This dashboard helps teams distinguish between fresh bugs potentially introduced by recent deployments and recurring technical debt that has accumulated over longer periods.

The "New vs. Existing Issues" visualization segments errors to make regression detection immediate and obvious. After a deployment, you can instantly spot if new issue patterns have emerged, separating them from the background noise of known issues. This segmentation transforms post-deployment validation from guesswork into data-driven assessment.

Occurrence timelines track error spikes across the last 30 days using line charts that correlate system noise with business cycles or release schedules. These temporal views reveal patterns that might otherwise remain hidden—perhaps errors spike during month-end processing, or certain issues only manifest during peak business hours. Understanding these correlations helps teams move from reactive firefighting to proactive capacity planning.

The "Issues Last 7 Days" component provides a tabular breakdown of top issues, showing category (Apex, Flow, Bulk API), functional area, status, and frequency metrics. This ranked view makes prioritization straightforward—you immediately see which problems are generating the most noise and affecting the most users. The dashboard includes links directly to issue records, enabling rapid navigation from high-level overview to detailed investigation.

The Issues Dashboard excels at trend analysis, providing visual confirmation of whether system health is improving or degrading month over month. Leadership can track whether engineering investments in quality are paying dividends. Development teams can demonstrate the impact of technical debt reduction efforts. The longitudinal perspective transforms observability from a reactive debugging tool into a strategic system health indicator.

### The Triage Dashboard: Today's Errors and Impact

While the Issues Dashboard focuses on trends over time, the Triage Dashboard concentrates on immediate operational needs. This dashboard serves admins and support teams who need to identify and prioritize fires happening right now, in the current business day.

The "Today's Errors" breakdown organizes errors by functional area and source—Job Requests, Integrations, Contact operations, Background jobs, Apex execution. This segmentation enables intelligent routing, ensuring the right team gets notified immediately about problems in their domain. When an integration error occurs, the integrations team sees it highlighted. When a batch job fails, the data operations team knows instantly. This functional organization reduces mean time to response by eliminating the detective work of figuring out who should handle each problem.

User impact visualization transforms error prioritization from a technical exercise into a business-focused decision. The dashboard distinguishes between background system errors that users never see and failures that actively prevent someone from completing their work. A gauge showing affected user count provides immediate context—is this error stopping 50 sales reps from closing deals, or is it a nightly batch process affecting no interactive users? This distinction guides resource allocation toward problems with genuine business consequences.

Data impact charts visualize which objects are experiencing failures—Contacts failing to save, Cases failing to update, Opportunities stuck in workflow errors. This object-level view helps teams understand not just that errors are occurring, but what business data is at risk. When paired with user impact metrics, these visualizations paint a complete picture of business disruption, not just technical dysfunction.

The Triage Dashboard dramatically reduces time to resolution by pinpointing functional areas and affected users instantly. Rather than asking "What's broken?", teams can ask "Who's affected and which team needs to fix it?" This shift accelerates incident response and improves user satisfaction by ensuring high-impact issues receive appropriate urgency.

### The Automation Dashboard: Technical Deep Dive

The Automation Dashboard serves developers and architects who need granular visibility into code quality, specific automation failures, and team resolution velocity. While other dashboards focus on business impact and operational health, this dashboard zeroes in on technical root causes and remediation patterns.

Detailed breakdowns of Apex errors and Flow failures rank specific classes and flows by error volume, showing developers exactly where their refactoring efforts will yield the highest return. The "Top Failing Flows" chart might reveal that a single flow accounts for 30% of all automation errors—an obvious candidate for immediate attention. The "Top Errors by Class" visualization might show that one Apex class appears in stack traces far more frequently than others, suggesting architectural problems or missing error handling.

Error type categorization groups exceptions by their nature—NullPointerExceptions, DML exceptions, CPU time limit exceeded, too many SOQL queries. This classification highlights systemic coding patterns that need addressing. If NullPointerExceptions dominate, the team needs to improve null checking. If governor limit exceptions are prevalent, automations need optimization for bulk processing. The categorization transforms individual errors into actionable improvement areas.

Resolution tracking shows the ratio of actioned versus unresolved issues over 120 days, providing visibility into team responsiveness and velocity. This historical view reveals whether the backlog of known issues is growing or shrinking, whether resolution pace is accelerating or stagnating. The tracking becomes a key performance indicator for technical quality management, showing whether the team is winning or losing the battle against technical debt.

The Automation Dashboard helps identify automations hitting Salesforce governor limits, showing which components are pushing resource boundaries. This visibility enables proactive optimization before limits cause production failures. Development teams can prioritize refactoring efforts based on actual resource consumption patterns rather than guesswork.

By highlighting the most brittle parts of the codebase and quantifying technical debt by volume and impact, the Automation Dashboard turns abstract quality concerns into concrete remediation priorities. Architects can make data-driven decisions about where to invest refactoring effort, and managers can demonstrate technical health improvements through measurable metrics over time.

## Understanding Dashboard Components

The dashboard uses various chart types to communicate different aspects of your error data. Bar charts show volume comparisons across categories or time periods. Donut charts illustrate proportional relationships, such as the percentage breakdown of error types. Line charts reveal trends over time, making it easy to spot spikes or improvements. Each visualization is designed to be understood at a glance while providing links to drill down into the underlying data.

Many dashboard components are interactive. Clicking on a chart element typically navigates you to a filtered view of the relevant logs or issues, bridging the gap between high-level visualization and detailed investigation. This interactivity transforms the dashboard from a passive monitoring tool into an active starting point for troubleshooting.

## Report Extensibility

While the homepage dashboard addresses common monitoring needs, every organization has unique questions they want to answer about their error data. Pharos's native architecture means you can build custom reports using standard Salesforce reporting tools. If you know how to create a Salesforce report, you can create reports for Pharos logs and issues.

Custom reports might analyze error patterns specific to your business processes, track metrics aligned with your operational KPIs, or provide specialized views for different stakeholders. A support team might build reports showing errors correlated with customer complaints. A development team might create reports tracking error trends across sprint cycles. A DevOps team might build reports that compare pre-deployment and post-deployment error rates.

The full range of Salesforce reporting capabilities applies to Pharos data. You can create summary reports with groupings and subtotals, matrix reports that cross-tabulate multiple dimensions, or joined reports that combine data from logs, issues, and related objects. Formulas, filters, and conditional highlighting all work as expected, giving you sophisticated analytical tools for understanding your observability data.

## Building Custom Dashboards

Beyond individual reports, you can assemble custom dashboards that combine multiple reports into a unified view. These dashboards can be tailored to specific roles, teams, or operational contexts. A release management dashboard might focus on comparing error rates across deployment windows. A hypercare dashboard might emphasize real-time metrics and recent error trends. An executive dashboard might present high-level metrics without excessive technical detail.

Salesforce dashboard components—charts, tables, metrics, gauges—all work with Pharos reports. You can configure automatic refresh schedules to ensure dashboard data stays current. You can set up subscriptions to deliver dashboard snapshots via email on a regular cadence, providing digest-style updates without requiring users to log in and check manually.

## Dashboards for Different Audiences

Different stakeholders need different views of the same underlying data. Technical teams benefit from dashboards showing specific error types, stack traces, and detailed categorization. Support teams need visibility into user-impacting issues and trends in customer-facing errors. Leadership wants high-level metrics on system stability and team responsiveness to issues.

Creating role-specific dashboards ensures each audience gets relevant information without overwhelming them with unnecessary detail. A developer dashboard might include charts breaking down Apex errors by class and method, while a support dashboard emphasizes errors affecting external users. These customized views promote broader adoption of observability practices across your organization.

## Trend Analysis and Historical Context

Reports and dashboards excel at revealing patterns that aren't obvious when looking at individual log records. You might discover that certain errors spike during specific times of day, indicating load-related issues. You might notice that error rates correlate with particular business processes or events. You might identify slow degradation in a system component that's been gradually failing over weeks or months.

This historical context transforms reactive troubleshooting into proactive system management. Rather than simply responding to individual errors, you can identify systemic issues, predict future problems, and measure the effectiveness of fixes over time. Reports become not just diagnostic tools but strategic assets for maintaining system health.

## From Insights to Action

The ultimate value of reports and dashboards lies in the actions they inspire and the priorities they clarify. Pharos dashboards transform raw log data into actionable intelligence by separating user impact from system noise, enabling teams to make informed decisions about where to invest engineering effort.

A chart showing increasing error volume prompts investigation. A breakdown by functional area triggers routing issues to the appropriate team. A trend analysis identifies the need for refactoring or optimization. But beyond these tactical responses, the dashboard architecture supports three strategic imperatives that define effective Salesforce operations.

**Protecting Revenue Operations** becomes possible when dashboards distinguish between errors that affect working users and background noise that doesn't. The Triage Dashboard's user impact metrics ensure that errors stopping salespeople from closing deals receive immediate attention, while technical issues with no user impact get prioritized appropriately. This user-first approach aligns technical work with business value, ensuring that observability investments protect revenue-generating activities.

**Monitoring Release Quality** transforms deployment validation from a hope-based exercise into an evidence-based practice. The Issues Dashboard's "New vs. Existing" segmentation spots regressions immediately after releases, providing early warning of problematic deployments. Teams can compare error rates before and after changes, quantify the impact of hotfixes, and build confidence in their release processes through measurable quality trends.

**Reducing Technical Debt** shifts from an abstract goal to a concrete program when dashboards highlight the most brittle parts of the codebase. The Automation Dashboard ranks flows and classes by failure frequency, showing developers exactly where refactoring yields the highest return on investment. Technical debt reduction becomes data-driven, measurable, and demonstrable to stakeholders who need to understand why engineering teams spend time improving code that "already works."

By combining Pharos's built-in homepage dashboards with custom reports and dashboards tailored to your needs, you create a comprehensive observability layer that serves multiple purposes—daily monitoring, deep analysis, executive visibility, and trend-based planning. The native Salesforce implementation ensures this powerful analytical capability integrates seamlessly into your existing workflows and skillsets, while the dashboard specialization ensures each stakeholder gets the specific insights they need to drive their part of the quality and stability mission.
