Start a production investigation from a pull request

Ask about a concrete symptom from a pull request in a repository linked to the affected environment. The comment author needs write access to that repository.

Post the question and check the reply#

  1. Start a comment on the pull request with a mention of Proofline, then write investigate and the symptom, for example @prooflinedev investigate checkout returns 502. The comment can be on the conversation or in a review comment thread.
  2. If the repository belongs to several environments, name one of them as a separate word or phrase, by the name Proofline shows for it or by its key, for example @prooflinedev investigate production: checkout returns 502.

Proofline reads the question up to the first horizontal rule outside a code block, such as a line of --- after an empty line. Text below the rule, such as a signature, is not part of the question.

A comment with no symptom after investigate, or with a symptom longer than 4,000 bytes, starts nothing. The reply says which. Comment again with a symptom, or with a shorter one.

Proofline posts nothing when the investigation starts. Its only reply is the answer.

When the repository belongs to only one environment, Proofline selects it without its name in the symptom. With several environments, a symptom that opens with one environment's name or key and a colon starts in that environment, whatever else the symptom names. Without that opening, if the symptom names none or more than one, nothing starts. The reply says which environments the symptom named and lists the environments by name, adding a key only when two share a name. A name then counts wherever it appears as a separate word or phrase, including inside a quoted alert or metric name, such as CI in ci_check_vm_template_missing. Comment again with one environment's name or key and a colon before the symptom. If no environment includes the repository, the reply says so; link the repository to an environment first.

A commenter without write access starts nothing. If they are a collaborator on the repository, the reply says that write access is required.

Search help

Tab to a result. Enter to open. Escape to close.