Human Readable Indexer Metrics

Feature Request: Human-Readable Indexer Metrics

Problem Statement

Currently, the metrics provided for indexers display raw Deployment IDs. This makes it difficult to quickly identify which subgraph is responsible for a given metric.

Current Workflow

1.	Check indexer metrics.
2.	Copy/Paste the Deployment ID into an explorer or third-party tools.
3.	Manually identify the associated subgraph.

This process is cumbersome and time-consuming, especially when managing multiple deployments.

Proposed Solution

Enhance indexer metrics by including the human-readable display name of the subgraph alongside the Deployment ID. This would make the metrics more intuitive and eliminate the need for external lookups.

Data Source

The subgraph display name can be fetched using the following query on the network subgraph:

{
  allocations {
    subgraphDeployment {
      versions {
        subgraph {
          metadata {
            displayName
          }
        }
      }
    }
  }
}

Benefits

•	Simplifies workflow for indexers.
•	Reduces reliance on external tools to identify subgraphs.
•	Improves metric visibility and debugging efficiency.

Implementation Considerations

•	Extend the metric output to include the displayName from the network subgraph query.
•	Ensure backward compatibility so existing workflows relying on raw Deployment IDs remain unaffected.

Start by locating the indexer metrics output and the network subgraph query described in the issue. Trace how Deployment IDs are emitted, then determine how the subgraph displayName can be included while preserving the existing IDs; done means metrics identify subgraphs without breaking current consumers.