Repository navigation
feat(cli): list findings since a deploy - #215
Merged
Merged
Conversation
telemetry findings lists the alerts that opened and the checks that failed in a project's window, newest first, through the MCP server's list_findings tool. It exits with 3 when the window has a finding, so a CI step or a coding agent can check a deploy with --since. A deployment without the tool fails with server_unsupported.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
telemetry findingslists what telemetry.dev found wrong in a project, newest first: the alerts that opened and the checks that failed. A failed check is a fail score from an automatic pass/fail evaluator, such as an LLM judge. The command callslist_findings, a new tool of the telemetry.dev MCP server. Without--since, it lists the last 7 days.--sincealso takes the time of a deploy, so a CI step or a coding agent can ask what went wrong after the deploy.--kind alertor--kind checklists one kind.The command exits with 3 when the window has at least one finding, also with
--json, and with 0 when it has none. No other code uses 3, and a request that fails still exits with the code of its error. A deployment withoutlist_findingsfails withserver_unsupported. The README now says that this code also covers a command that the deployment doesn't have.In human output, the link of each finding is on its own line under its row, as
traceprints error text. A dashboard link often has more than 100 characters, so in a column it would take the width of the finding text.Tests that ran
vp test run tests/cli.test.tsinpackages/clipasses, and so doesvp check packages/cli.