> 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/search.md).

# Search

Find logs using standard Salesforce search functionality.

## Finding Logs Quickly

Sometimes you need to locate a specific log record without browsing through list views or analyzing dashboard charts. Perhaps you remember part of an error message, know the name of a failing flow, or have an issue number from a Slack notification. In these scenarios, Salesforce's standard global search functionality provides the fastest path to the information you need.

Because Pharos stores logs as native Salesforce objects, they participate fully in the platform's search infrastructure. The same global search bar that helps you find accounts, contacts, or cases works equally well for finding logs. This consistency means there's nothing new to learn—if you know how to search Salesforce, you know how to search for logs.

## Global Search Capabilities

The global search bar at the top of your Salesforce interface searches across multiple objects simultaneously, including Pharos logs. When you enter a search term, Salesforce scans searchable fields on the log object and returns matching records. This broad search happens quickly and returns results ranked by relevance, helping you find what you need even with partial or imprecise search terms.

Common search scenarios include looking for logs related to a specific flow by searching for its API name, finding errors containing particular text in their summary or details, locating logs associated with a certain user, or discovering errors related to specific record IDs or business objects. The global search handles all these cases naturally, returning results from whichever fields match your search criteria.

## Searchable Fields

Not every field on a Salesforce object is automatically searchable—the platform indexes specific fields to balance search performance with storage efficiency. For Pharos logs, searchable fields typically include the error summary, log names or identifiers, and potentially other key text fields depending on your configuration. Understanding which fields are searchable helps you craft more effective search queries.

If you find yourself frequently needing to search by fields that aren't currently indexed, you can work with your Salesforce administrator to add them to the search index. This customization ensures the search functionality aligns with your team's actual usage patterns and information needs.

## Search Techniques

Effective searching often involves more than just typing a single keyword. Salesforce search supports partial word matching, so you don't need to remember exact spellings or complete names. If you're looking for a flow called "Account\_Creation\_Validation\_Process" but only remember it's related to accounts, searching for "account" will surface relevant results.

For more precise results, you can search for specific phrases by enclosing them in quotes. This technique helps when you're looking for an exact error message or a specific sequence of words that appeared in a log summary. You can also combine multiple search terms to narrow results—searching for both a flow name and an error type might quickly isolate the specific log you need.

## From Search Results to Investigation

Search results appear as a list with snippets showing where your search terms matched within each record. The results page provides quick access to relevant logs without requiring navigation through multiple views or filters. Clicking on a search result takes you directly to the full log record, where you can see complete details, review the debug information, and investigate the error in context.

This direct path from search query to detailed information proves particularly valuable during incident response when speed matters. Rather than manually filtering list views or drilling through dashboards, you can jump straight to relevant logs based on whatever information you have available—a snippet from an error email, a field name mentioned by a user, or a component name from a stack trace.

## Search as Part of Your Workflow

While list views and dashboards serve as primary interfaces for routine monitoring and analysis, search complements these tools for ad-hoc investigation. During a troubleshooting session, you might start with search to locate initial examples of an error, then switch to a filtered list view to see all related occurrences, and finally pull up a dashboard to understand the broader trend.

Search also helps when you're following up on notifications or issues. A Slack notification might mention an issue number or flow name—you can copy that identifier directly into global search to find the corresponding log records. This seamless connection between different parts of your workflow reduces friction and keeps investigation moving quickly.

## Limitations and Alternatives

While global search handles many scenarios effectively, it has limitations. Search results are capped at a certain number of records, so if you're looking for all instances of a particular error, a filtered list view or report provides more comprehensive results. Search focuses on text matching rather than complex filtering logic, so queries involving date ranges, numeric comparisons, or multiple criteria are better handled through list view filters.

Understanding when to use search versus other access methods ensures you choose the right tool for each task. Search excels at quick lookup based on text fragments or identifiers. List views excel at browsing and filtering based on multiple criteria. Reports and dashboards excel at analysis and visualization. Together, they provide comprehensive access to your log data regardless of your starting point or objective.

## Integration with Broader Search Ecosystem

If your organization uses Salesforce Einstein Search or other advanced search capabilities, those enhancements also apply to Pharos logs. Features like natural language search, personalized results based on your usage patterns, and intelligent result ranking all work with log data just as they do with other Salesforce objects. This integration ensures your investment in Salesforce search infrastructure extends to your observability data.

The ability to search logs using familiar Salesforce search functionality removes barriers to adoption and reduces the learning curve for new team members. Anyone who knows how to use Salesforce can immediately find the logs they need, promoting broader engagement with observability data across your organization.
