Fill gaps from assistant conversations: Prometheus vs billing, multi-repo git metadata#446
Open
mintlify[bot] wants to merge 1 commit into
Open
Fill gaps from assistant conversations: Prometheus vs billing, multi-repo git metadata#446mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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.
Summary
Address two recurring assistant-conversation gaps: Prometheus check-result counter vs billing usage, and attaching git metadata across multiple source repositories.
Changes
integrations/observability/prometheus-v2.mdx: Note thatcheckly_check_result_totalcounts individual check-run results and is not intended to reconcile with billing usage; point to the billing view andcheckly accountCLI for actual plan usage.cli/attaching-git-metadata.mdx: Add a "Working with multiple repositories" section describing the supported pattern of runningcheckly test/checkly deployper-repo pipeline withCHECKLY_REPO_URLset for that repo, plus isolation guidance via groups/tags.Context
Recent assistant threads showed users confused about a mismatch between the Prometheus counter and billed usage, and asking whether git metadata could be attached from multiple repos (backend + frontend) — cases where the assistant had to infer answers not clearly stated in the docs.