docs: Prometheus V2 - update cache documentation

[clample]

Affected Components

• Content & Marketing
• Pricing
• Test
• Docs
• Learn
• Other

Pre-Requisites

• Code is linted (npm run lint)

Notes for the Reviewer

See https://github.com/checkly/checkly-backend/pull/6227

Prometheus V2 metrics will be cached for 50 seconds.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
checklyhq-com	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 24, 2025 1:06pm

[coderabbitai]

Walkthrough

The change updates the documentation for the Prometheus v2 integration. It adjusts the caching duration for responses from the Prometheus metrics endpoint, reducing it from 60 seconds to 50 seconds. The rate limit of 50 requests per minute and the recommended scrape interval of 60 seconds remain unchanged. There are no modifications made to any exported or public entity declarations.

Changes

File	Change Summary
site/.../prometheus-v2.md	Updated caching duration for Prometheus responses from 60 seconds to 50 seconds; other details unchanged.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[tnolet]

Vamos

[clample]

Thanks for the review @tnolet :)

The backend changes are still in-development. I'll merge this when the changes are deployed.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

site/content/docs/integrations/prometheus-v2.md (1)

46-47: Refine Cache Duration Wording

The cache duration update to 50 seconds is correct. However, the phrasing on line 46 ("cached during 50 seconds") is a bit awkward; it is more natural to say "cached for 50 seconds." This small nit-pick should help align the documentation with common usage.

Suggested diff:

- > The responses from this endpoint are cached during 50 seconds.
+ > The responses from this endpoint are cached for 50 seconds.

🧰 Tools

🪛 LanguageTool

[uncategorized] ~46-~46: The preposition “for” seems more likely in this position.
Context: ...responses from this endpoint are cached during 50 seconds. > Any request made to this ...

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b47f04e and d387246.

📒 Files selected for processing (1)

• site/content/docs/integrations/prometheus-v2.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

site/content/docs/integrations/prometheus-v2.md

[uncategorized] ~46-~46: The preposition “for” seems more likely in this position.
Context: ...responses from this endpoint are cached during 50 seconds. > Any request made to this ...

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION)