chore: added az/region metric for bytes transferred

[mayankpande88]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @mayankpande88, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the network bytes sent and received metrics by adding region and availability zone labels. This provides richer context for analyzing network traffic patterns based on the location of the involved workloads.

Highlights

• Metric Enhancement: Added src_region, src_az, destination_region, and destination_az labels to the container_net_tcp_bytes_sent_total and container_net_tcp_bytes_received_total metrics. This allows for more granular analysis of network traffic by geographical location.
• Data Collection Update: Modified the metric collection logic in containers/container.go to include the region and zone information for source and actual destination workloads when reporting bytes sent/received metrics.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configureGemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds new Prometheus metric labels for source/destination region and availability zone (AZ) to the NetBytesSent and NetBytesReceived counters. The changes involve updating the metric definitions in metrics.go and modifying the counter function calls in container.go to include these new label values.

My review highlights a couple of points:

1. A suggestion to improve the maintainability of the counter function calls in container.go by refactoring the long argument list, which has grown with the new labels.
2. A point of consideration regarding the semantic mapping of Workload.Zone to the _az (Availability Zone) labels to ensure data correctness.

Overall, the changes are straightforward and aim to enhance network traffic observability with more granular location-based data.