---
title: "Trace a lead to the resource named in a question | Proofline Help"
description: "When a question names a resource or cites a related alert, inspect the reasons under the ranked changes in Summary. Use the resource match to decide which change to investigate first."
url: https://proofline.sh/help/investigation-question-resource-leads/
---

[Help center](/help/)

# Trace a lead to the resource named in a question

When a question names a resource or cites a related alert, inspect the reasons under the ranked changes in Summary. Use the resource match to decide which change to investigate first.

## Read question-specific ranking reasons

Two reasons appear only in a question's investigation:

-   **resource the question named**: the question held, as a whole word, the name of a Cloud Run service or Cloud SQL instance, of an ECS service, a Lambda function, or an RDS instance or cluster, or of an Azure resource other than a subscription or resource group, and the lead changed that resource's configuration, or that of one of its Cloud Run or Azure container app revisions or Lambda function versions. A name with an underscore counts only whole, and an underscore also ends a word, so `orders_db` names the Lambda function `orders_db`, and a resource called `orders` or `db`, but not `orders_db_v2`. It ranks above the other leads with the same timing, as the alert reasons above do. In Slack and pull request replies, such a lead reads "Configuration change to a resource the question named". The name only reorders the changes the investigation read; it adds no read. [Ask Proofline to investigate](/help/ask-for-investigation/#name-the-service-or-instance) explains how to name one.
-   **resource a related alert named**: the lead changed the configuration of a resource that one of the question's related alerts named: a Cloud Run service that the alert's metric counted, the Cloud Run service or Cloud SQL instance that the alert names, an asset that one of its metric labels named, the resource that a CloudWatch alarm's metrics name, or the resource that an Azure Monitor alert targets, as **resource the alert named** describes. Only a related alert that gave the question telemetry counts. The lead ranks above the other leads with the same timing, as **resource the question named** does. In Slack and pull request replies, such a lead reads "Configuration change to a resource a related alert named", which names neither the alert nor the resource. **Related alerts** in **Evidence** links the alerts the question used. The reason only reorders the changes the investigation read; it adds no read.

None of these reasons states a cause or rules a lead out.

## Related guides

-   [Find an environment's investigations](/help/environment-investigations/)
-   [Create an environment](/help/create-environment/)
