Skip to content

DOCS-2955: Add Usage API doc for Calico Cloud#2837

Open
ctauchen wants to merge 4 commits into
tigera:mainfrom
ctauchen:cc-usage-api-docs-2955
Open

DOCS-2955: Add Usage API doc for Calico Cloud#2837
ctauchen wants to merge 4 commits into
tigera:mainfrom
ctauchen:cc-usage-api-docs-2955

Conversation

@ctauchen

@ctauchen ctauchen commented Jul 7, 2026

Copy link
Copy Markdown
Collaborator

Adds a new operations page documenting how to create a read-only API key in the web console and use it to call the Calico Cloud Usage API for vCPU usage and managed cluster data. Adds the page to the operations sidebar after usage-metrics.

Copilot AI review requested due to automatic review settings July 7, 2026 15:30
@ctauchen ctauchen requested a review from a team as a code owner July 7, 2026 15:30
@netlify

netlify Bot commented Jul 7, 2026

Copy link
Copy Markdown

Deploy Preview succeeded!

Built without sensitive environment variables

Name Link
🔨 Latest commit 6615984
🔍 Latest deploy log https://app.netlify.com/projects/tigera/deploys/6a4d1f967efe870008162e05
😎 Deploy Preview https://deploy-preview-2837--tigera.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 88 (🟢 up 1 from production)
Accessibility: 98 (no change from production)
Best Practices: 92 (no change from production)
SEO: 100 (no change from production)
PWA: -
View the detailed breakdown and full score reports

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

@netlify

netlify Bot commented Jul 7, 2026

Copy link
Copy Markdown

Deploy Preview for calico-docs-preview-next ready!

Name Link
🔨 Latest commit 6615984
🔍 Latest deploy log https://app.netlify.com/projects/calico-docs-preview-next/deploys/6a4d1f964e0bb60008109ab8
😎 Deploy Preview https://deploy-preview-2837--calico-docs-preview-next.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.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Adds a new Calico Cloud operations doc that explains how to generate a read-only API key in the web console and use it to run generated commands against the Usage API, and wires the new page into the operations sidebar.

Changes:

  • Added a new operations/usage-api documentation page describing API key creation and Usage API invocation.
  • Updated the Calico Cloud sidebar to include the new page after usage-metrics.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
sidebars-calico-cloud.js Adds the new operations/usage-api doc to the Calico Cloud operations navigation.
calico-cloud/operations/usage-api.mdx New how-to page for generating an API key and using the Calico Cloud Usage API.

Comment thread calico-cloud/operations/usage-api.mdx Outdated

## Prerequisites

* You are signed in to the web console as a user with the **Admin** and **Usage Metrics** roles, or the **Owner role**.
Comment thread calico-cloud/operations/usage-api.mdx Outdated

## Additional information

* [Usage metrics](usage-metrics.mdx)
ctauchen added 2 commits July 7, 2026 16:41
Documents creating a read-only API key in the web console and using it
to call the Usage API for vCPU usage data. Adds the page to the
operations sidebar after usage-metrics.
@ctauchen ctauchen force-pushed the cc-usage-api-docs-2955 branch from fb2abc2 to 9d4e352 Compare July 7, 2026 15:41
@ctauchen

ctauchen commented Jul 7, 2026

Copy link
Copy Markdown
Collaborator Author

@asincu PTAL


1. In the web console, click the user icon <IconUser width="20"/> **> Settings**.
1. Under the **API Keys** tab, click **Generate new key**.
1. Enter a description, choose a validity period, and then click **Create**.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

We will be changing description to name

* **Managed clusters** — per-cluster usage rows, with optional project filtering and CSV output.
* **Contracts** — your organization's contracts, including start and end dates, vCPU hours, package, and add-ons.
1. Copy the generated command.
1. In the command, replace `<your-secret>` with your API key, and set any query parameters, such as `startTime`, `endTime`, and `granularity`, for your query.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@asincu Should we mention in docs that the daily granularity limit of 93 days? (~3 months) and for monthly granularity is 3 years (36 months)?

{
    "key": "time_range.too_large",
    "message": "daily granularity is limited to a maximum range of 93 days"
}

{
    "key": "time_range.too_large",
    "message": "monthly granularity is limited to a maximum range of 36 months"
}

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.

4 participants