Country or region and language

    Choose your country or region and your language.

    Suggested for you

      All countries and regions

        Choose your character

        It shows in the top bar and on your profile. Change it any time.

        Google Cloud Logging filters and incident evidence

        Choose the population before interpreting its errors. A plausible result can still describe another service or the wrong slice of an incident.

        Checked 14 November 2026

        A dispatch-service handoff

        A fictional incident asks for Cloud Run revision errors from one dispatch service. Filter the project, resource type, service field and severity. Read the requested sort order and limit as part of the question; the earliest matching records are different from the newest ones.

        The Logging lesson queries original fixed entries. Change a relevant field or include an extra population and observe how the result changes. The handoff requires the exact requested rows, not just one correct-looking entry among unrelated records.

        Silence and coverage

        An empty result doesn’t prove health.

        Check ingestion, the actual source and the filter before treating absence as evidence. A successful local query also doesn’t establish coverage of a production incident.

        The adapter supports equality, severity comparison, AND, ordering and a bounded limit. It doesn’t implement the full Logging language or read live logs. Continue in the Google Cloud course for monitoring and response decisions, or use BigQuery for supported analytical SQL.

        Sources

        Your Work Gym account

        Save your progress and pick up on another device. Your browser's progress comes with you.

        or

        You can keep practicing without an account.

        Help and feedback

        Ask a question, tell us what is not working, or share an idea. We reply by email.

        What is it about?

        We use it only to reply to you.