Skip to content

Update Anthropic cost data latency to 24-48 hours#24581

Draft
xaviersicotte wants to merge 1 commit into
masterfrom
xavier.sicotte/docs-15132-anthropic-cost-latency
Draft

Update Anthropic cost data latency to 24-48 hours#24581
xaviersicotte wants to merge 1 commit into
masterfrom
xavier.sicotte/docs-15132-anthropic-cost-latency

Conversation

@xaviersicotte

Copy link
Copy Markdown

What does this PR do?

Updates the Anthropic Usage and Costs integration README to say cost data appears in Cloud Cost Management within 24-48 hours, instead of 24 hours.

Motivation

Fixes DOCS-15132

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
  • Add qa/required if this PR needs QA validation, or qa/skip-qa if it does not. Exactly one of the two is required.
  • If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

Cost data in Cloud Cost Management for the Anthropic Usage and Costs
integration was documented as appearing within 24 hours; update to
24-48 hours to reflect actual latency.
@dd-octo-sts

dd-octo-sts Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Validation Report

All 21 validations passed.

Show details
Validation Description Status
agent-reqs Verify check versions match the Agent requirements file
ci Validate CI configuration and code coverage settings
codeowners Validate every integration has a CODEOWNERS entry
config Validate default configuration files against spec.yaml
dep Verify dependency pins are consistent and Agent-compatible
http Validate integrations use the HTTP wrapper correctly
imports Validate check imports do not use deprecated modules
integration-style Validate check code style conventions
jmx-metrics Validate JMX metrics definition files and config
labeler Validate PR labeler config matches integration directories
legacy-signature Validate no integration uses the legacy Agent check signature
license-headers Validate Python files have proper license headers
licenses Validate third-party license attribution list
metadata Validate metadata.csv metric definitions
models Validate configuration data models match spec.yaml
openmetrics Validate OpenMetrics integrations disable the metric limit
package Validate Python package metadata and naming
qa-label Validate the pull request declares whether it needs QA for the next Agent release
readmes Validate README files have required sections
saved-views Validate saved view JSON file structure and fields
version Validate version consistency between package and changelog

View full run

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant