Fix order of job groups and otel tests

[hasit]

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

  • Enhanced telemetry capabilities for specific pipeline configurations.

• Bug Fixes

  • Improved shutdown sequence for quota scheduler and rate limiter components to ensure proper operation order.

[coderabbitai[bot]]

Walkthrough

The changes involve conditional logic and order of operations adjustments in a Go codebase. Specifically, a conditional check was added to modify a configuration for a metrics pipeline, and the shutdown sequences for job groups in quota-scheduler and rate-limiter components were reordered, which could affect how resources are released or synchronized.

Changes

File Path	Change Summary
.../otel/otel_test.go	Added a conditional check to append "attributes/agent_group" for a specific pipelineName.
.../flowcontrol/.../quota-scheduler.go .../flowcontrol/.../rate-limiter.go	Swapped the order of Stop calls for different job groups in shutdown procedures.

🐇✨ In the realm of code, where logic threads weave, A rabbit hopped through, changes to conceive. With a flip and a swap, the order's made neat, Now the code hops along, with nary a beat. 🌟 🐰💻

---

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 .` - `Generate unit-tests for this file.` - 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 tests 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 generate interesting stats about this repository from git and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit tests.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` 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 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](https://coderabbit.ai/integrations/coderabbit-overrides.v2.json). - 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` ### CodeRabbit Discord Community Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback.