In the Guidewire Cloud Platform (GWCP) ecosystem, Observability is primarily handled through the integration with Datadog. Developers use Datadog to monitor the health of their " Planets " and to perform deep-dive troubleshooting of application logs. Navigating through millions of log lines requires efficient filtering and searching techniques.

The two primary methods taught in the " Developing with Guidewire Cloud " course for finding specific log entries are sidebar facets and the search bar. Sidebar facets (Option D) are structured filters based on log metadata. In a Guidewire context, these facets allow a developer to quickly narrow down logs by specific criteria such as the " Planet " (Dev, Pre-prod), the specific " Service " (ClaimCenter, BillingCenter), the " Log Level " (Error, Warn), or even a specific " Trace ID. " This structured approach is essential for isolating errors to a specific environment or time window.

Complementing this is the search bar for full-text searches (Option F). This allows developers to search for specific strings within the log message itself—such as a specific Claim Number, a unique Exception class name, or a custom log prefix defined in Gosu code. By combining full-text search with facet filtering, developers can rapidly pinpoint the exact root cause of a production or development issue.

Other options are related to the cloud ecosystem but do not serve the specific purpose of finding information within logs. TeamCity (Option C) is for builds, not log analysis; and while Monitors (Option B) and Dashboards (Option E) provide higher-level views or alerts, they are not the primary tools for searching through the raw log data during an active troubleshooting session.