Add counter panels to rate limiter dashboard

[karansohi]

Description of change

Checklist

• Tested in playground or other setup
• Screenshot (Grafana) from playground added to PR for 15+ minute run
• Documentation is changed or added
• Tests and/or benchmarks are included
• Breaking changes

Summary by CodeRabbit

• New Features

  • Introduced a new row with a time series panel for enhanced data visualization on the rate limiter dashboard.
  • Expanded dashboard content with additional statistical panels for more comprehensive data analysis.

• Refactor

  • Improved dashboard layout to accommodate new visual elements and data queries.

[coderabbitai]

Walkthrough

The Grafana dashboard has been updated with a new layout, introducing an additional row for time series visualization and reconfiguring the existing row to display statistics. This enhances the dashboard's capability to provide both detailed metrics at a glance and trends over time.

Changes

File Path	Change Summary
.../summary/rate-limiter/rows.libsonnet	Added row2 with timeSeriesPanel; reconfigured row1 with three statPanel elements; updated targets with a new query

🐇✨
To panels of stats, we hop and we add,
A row for time's flow, in new data clad.
With queries a-twirl, our dashboards we craft,
In Grafana's realm, where data's draught.
📈🎉

---

Tips

Chat with CodeRabbit Bot (@coderabbitai)

• You can reply to a review comment made by CodeRabbit.
• You can tag CodeRabbit on specific lines of code or files in the PR by tagging @coderabbitai in a comment.
• You can tag @coderabbitai in a PR comment and ask one-off questions about the PR and the codebase. Use quoted replies to pass the context for follow-up questions.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 4b76367 and a48e672.

Files selected for processing (1)

• dashboards/grafana/dashboards/summary/rate-limiter/rows.libsonnet (4 hunks)

Additional comments: 5

dashboards/grafana/dashboards/summary/rate-limiter/rows.libsonnet (5)

• 1-4: The addition of statPanel and timeSeriesPanel imports aligns with the PR's objective to enhance the dashboard with new panels. Ensure that these new imports are used correctly in the dashboard configuration.

• 11-45: The new row1 contains three statPanel elements with different metrics. Verify that the metrics 'Total Requests', 'Total Accepted Requests', and 'Total Rejected Requests' are correctly calculated and that the panels are configured with appropriate properties such as x, h, w, panelColor, graphMode, noValue, and unit.

• 48-50: The targets variable has been expanded with a new Prometheus query. Ensure that the new query is correct and that it integrates seamlessly with the existing queries, especially considering the use of $__rate_interval and the withIntervalFactor(1) method.

• 56-62: > Note: This review was outside the patches, so it was mapped to the patch with the greatest overlap. Original lines [59-67]

The new row2 with a timeSeriesPanel is added for 'Aperture Rate Limiter'. Confirm that the axisLabel and unit are set correctly and that the targets variable is properly integrated into the panel.

• 69-69: The final dashboard layout is an array containing row1 and row2. Ensure that this layout is consistent with the intended design and that the order of rows reflects the dashboard's logical flow.