feat(collector): timestamps and offset fields

[tothandras]

Summary by CodeRabbit

• New Features

  • Introduced configurable delay settings for Prometheus metrics collection, enabling users to adjust how far back the system scrapes data.
  • Updated AI metrics configuration by renaming and refining timing settings for a clearer offset specification.

• Bug Fixes

  • Improved metrics reporting by selecting the latest available measurement.
  • Standardized timestamp handling so that both metric outputs and scheduled events are consistently reported in UTC.

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

This pull request introduces configurable offsets and enforces consistent UTC timestamp handling across multiple input modules. In the Prometheus input, a new query offset is added and integrated into configuration, scraping, and metadata. In the RunAI input, an existing metrics offset is renamed and its usage updated in scraping and batch processing. The metrics retrieval functions now select the latest metric value and convert timestamps to UTC, and the schedule input is updated to assign timer values in UTC.

Changes

File(s)	Change Summary
collector/benthos/input/prometheus.go collector/benthos/input/run_ai.go	Offset Configuration Updates: Introduced a new query_offset constant and field in Prometheus input and renamed the metrics offset field in RunAI input. Adjustments include configuration parsing, scraping logic, and metadata updates with consistent UTC time usage.
collector/benthos/input/runai/metrics.go	Metric Handling Enhancements: Changed metric value selection to use the last entry in the values array and modified timestamp handling to enforce UTC formatting for workload and pod metrics.
collector/benthos/input/schedule.go	Time Conversion Consistency: Updated the ReadBatch method to assign timer channel values in UTC format.

Possibly related PRs

• feat(collector): prometheus input #2425: Contains related modifications in the Prometheus input module, particularly affecting the integration and processing of offset settings.

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
  - To enable this feature, set early_access to true under in the settings.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 59e49c2 and a0c5d4b.

📒 Files selected for processing (4)

• collector/benthos/input/prometheus.go (7 hunks)
• collector/benthos/input/run_ai.go (10 hunks)
• collector/benthos/input/runai/metrics.go (4 hunks)
• collector/benthos/input/schedule.go (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 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.