Skip to content

Conversation

@kvaps
Copy link
Member

@kvaps kvaps commented Jan 16, 2026

Summary

Update telemetry documentation to reflect the new split architecture between cozystack-operator and cozystack-controller.

Changes

  • Document that telemetry is now collected by two components
  • Update example payload with new metrics format
  • Add cozy_cluster_capacity metric (cpu, memory, GPU)
  • Add cozy_package_info metric for installed packages
  • Replace cozy_workloads_count with cozy_application_count
  • Remove cozy_tenants_count (now cozy_application_count{kind="Tenant"})

Related

Depends on: cozystack/cozystack#1869

Test plan

  • Review rendered documentation
  • Verify payload examples are accurate

Update telemetry documentation to reflect the new split architecture:
- cozystack-operator collects cluster-level metrics
- cozystack-controller collects application-level metrics

Updated metrics:
- Added cozy_cluster_capacity for cpu, memory, GPU resources
- Added cozy_package_info for installed packages
- Added cozy_application_count for application instances
- Removed cozy_workloads_count (replaced by cozy_application_count)
- Removed cozy_tenants_count (now counted as cozy_application_count{kind="Tenant"})
- Removed bundle/oidc labels from cozy_cluster_info

Co-Authored-By: Claude <noreply@anthropic.com>
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 16, 2026

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

@netlify
Copy link

netlify bot commented Jan 16, 2026

Deploy Preview for cozystack ready!

Name Link
🔨 Latest commit 439f23f
🔍 Latest deploy log https://app.netlify.com/projects/cozystack/deploys/696a84ada877990008fd5f4d
😎 Deploy Preview https://deploy-preview-400--cozystack.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @kvaps, I'm Gemini Code Assist1! 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 updates the telemetry documentation to align with a new split architecture, where telemetry data is collected by both cozystack-operator and cozystack-controller. The changes clarify which component collects what type of data and provide revised examples of the telemetry payload, incorporating new metrics for cluster capacity and installed packages, while also updating existing metric names and structures.

Highlights

  • Telemetry Architecture Update: Documentation now reflects that telemetry is collected by two distinct components: cozystack-operator and cozystack-controller.
  • Metrics Format Update: The example telemetry payload has been updated to reflect the new metrics format.
  • New Cluster Capacity Metric: Added cozy_cluster_capacity metric to capture CPU, memory, and GPU resources.
  • New Package Information Metric: Introduced cozy_package_info metric to track installed packages.
  • Workload Count Metric Renamed: The cozy_workloads_count metric has been replaced with cozy_application_count.
  • Tenant Count Metric Refinement: The cozy_tenants_count metric has been removed, with tenant counts now represented by cozy_application_count{kind="Tenant"}.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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 configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request effectively updates the telemetry documentation to align with the new split architecture, separating metrics from cozystack-operator and cozystack-controller. The new metrics like cozy_cluster_capacity and cozy_package_info are well-documented, and the payload examples are updated clearly. My review includes a minor suggestion to improve the grammar in one sentence for better readability. Overall, the changes are accurate and improve the documentation.

### Example of Telemetry Payload:

Below is how a typical telemetry payload looks like in Cozystack:
Below is how a typical telemetry payload looks like in Cozystack.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For better readability and grammatical correctness, consider rephrasing this sentence. The construct "how ... looks like" is generally considered incorrect; "what ... looks like" or "how ... looks" are the preferred forms.

Suggested change
Below is how a typical telemetry payload looks like in Cozystack.
Below is an example of a typical telemetry payload in Cozystack.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants