https://github.com/sourcegraph/sourcegraph/issues/62295 surfaced problems with debugging timeout and generic problems that lead to incomplete data points. The documentation says that the user should reduce the scope of the query, but we see that customers prefer to run queries over all of their repositories. I'm not sure how we would bisect repositories to exclude the problematic ones.

Our GraphQL schema for TimeoutDatapointAlert and GenericIncompleteDatapointAlert contains the time and maybe a generic reason that something went wrong.

We could help users that don't have access to logs by exposing the repository/repositories that caused problems.

Example:

type GenericIncompleteDatapointAlert implements IncompleteDatapointAlert {
    """
    The data point that is incomplete.
    """
    time: DateTime!

    """
    A message describing why the datapoint was marked incomplete.
    """
    reason: String!

    """
    The repositories that this data point is incomplete for.
    """
    repositories: [String!]!
}

As a next step we could surface this information in our UI, but including this info in our GraphQL should be a good start.