CloudHealth now supports Anthropic Claude Enterprise cost and usage through dataconnect. Customers can now see cost and usage per model type, user, RBAC group, organization and more.
To configure Anthropic data connect, a Claude Enterprise Admin must log into Claude and complete the following steps.
Organization ID: The unique identifier for your Anthropic organization, available under Settings > Account in the Anthropic Console.
Analytics API Key: Generate the Analytics API key with the following read-only scopes: read:org_audit, read:analytics, read:spend_limits, read:members, and read:rbac_groups.
After your key has been created, navigate to Data Connect → New Connection and select Anthropic.
After collection finishes you can find the dataset and report by navigating to Anthropic Cost and Usage in Either Section.
A Note on Claude Platform - At this time Claude Platform requires an Admin key with write privileges in order to ingest Cost and Usage data per user. For this reason CloudHealth has not decided to support Claude Platform in this release while we pursue alternative ways of authentication that are less privileged.
To support customers with sensitive data requirements around PII, Data Connect now supports an "Exclude Sensitive Data” option. By toggling this on, fields like User Name, Email Address will be dropped from collection. Dropped fields will show as “-” in the dataset
You can find this option in the schema step, and can toggle it on or off at any time. Changing the setting in subsequent months will replace the values historically. This option is available in all branded connectors.
CloudHealth now collects and processes Project Name, Project ID, User Names and User Emails in the OpenAI cost and usage dataset. These fields are included as new dimensions in the standard report. Customers now have the ability to pivot cost and token consumption by projects and users for direct cost allocation back to the cost drivers of AI.
To enable these fields, toggling sensitive data in Data Connect must be turned off, and OpenAI Dataconnect must be configured with a read only key. If you previously configured with a scoped RBAC key, it is recommended you change your configuration to a read only key at this time in order to future proof future releases.
KPI widgets in dashboards will now allow for time granularity selections during configuration. Customers can select from all granularities supported in the backing report.
Users are now able to unsubscribe from reports within the email they receive for that report.
We have released support for sharing reports and datasets that have been created in any OU with all Child OUs. Previously only supported at the TLOU, users in subOUs can now share content with all child orgs by selecting “Publish to Child Orgs” . This action is available from the Reports or Datasets page
We have added support for Statement Detail for Azure for all bill types! Now available from the Statements page, it is now possible to view the configuration detail for all Azure bill types. With this release, we now have consistent support across all clouds
Fixed a bug where charts showed $NaN in the total row
Commitment coverage widget drilldown from Realized Savings will now automatically match values
Resolved an issue where certain filters did not get applied on drilldowns from KPI widgets
Preserving Realized Savings dashboard filters when coming from drilldown page
After creating a custom report, users are now redirected to the Custom Reports tab instead of Standard Reports
Fixed an issue that caused Tag columns to be removed in the custom dataset page. The selected tag column will now automatically appear under the relevant list inside the filter panel
Cost History, expanded the inclusion of a "Select All" option in filters to allow more than a single selection
Resolved an issue where deleted dashboards would still appear in the Dashboard Management page until refresh