Revert "Revert "Cloud actions (#4450)" (#4463)" (#4465)

This reverts commit 311eff3.

Author: brianmacdonald-temporal

docs/best-practices/cost-optimization.mdx

@@ -137,7 +137,7 @@ For detailed discussion of this tradeoff, see [How many Activities should I use
 
 ### Child Workflows vs Activities
 
-[Child Workflows cost 2 Actions](/cloud/actions#child-workflows) compared to an Activity's 1 Action.
+[Child Workflows cost 2 Actions](/cloud/actions#workflow) compared to an Activity's 1 Action.
 See [Child Workflows documentation](/child-workflows) for detailed comparison of capabilities and use cases.
 
 ### Retry Policies
@@ -165,7 +165,7 @@ Refer to this blog post on [Mastering Workflow retry logic for resilient applica
 ### Local Activities
 
 A [Local Activity](/local-activity#local-activity) is an Activity Execution that executes in the same process as the Workflow Execution that spawns it.
-Therefore, multiple Local Activities that run back-to-back only [count as a single billable action](/cloud/actions#activities), whereas each regular Activity counts as a billable action.
+Therefore, multiple Local Activities that run back-to-back only [count as a single billable action](/cloud/actions#activity), whereas each regular Activity counts as a billable action.
 However, there are tradeoffs to converting regular Activities to Local Activities.
 For example, if a specific Local Activity fails, *all* of them will be retried together.
 Review [the docs](/local-activity) or reach out to your account team to learn more.
@@ -189,7 +189,7 @@ Use Regular Activities instead of Local Activities if you require any of the fol
 2. For Search Attributes that must be updated during Workflow Execution, each `UpsertSearchAttributes` call counts as 1 Action regardless of how many attributes are updated.
    Batch multiple related attribute updates into single operations to reduce Actions consumed.
 
-See the [Temporal Cloud Action Documentation](/cloud/actions#workflows) for details.
+See the [Temporal Cloud Action Documentation](/cloud/actions#workflow) for details.
 
 #### Signal handling
 
@@ -252,7 +252,7 @@ Alternatively, if you are looking to do analysis on closed Workflow Executions,
 ### Validation approach
 
 1. **Test in non-production**: Validate functional correctness before production deployment
-2. **Monitor comprehensively**: Leverage the [Usage dashboard](/cloud/actions#usage) in the Cloud UI to track the impact on Actions and Storage after optimizations are made
+2. **Monitor comprehensively**: Leverage the [Usage dashboard](/cloud/actions-usage#usage) in the Cloud UI to track the impact on Actions and Storage after optimizations are made
 3. **Progressive rollout**: Deploy to a small percentage, validate, then expand. Review the [Worker Versioning documentation](/production-deployment/worker-deployments/worker-versioning) to learn about rolling out changes to Workflows
 4. **Continuous review**: Re-evaluate optimization effectiveness quarterly as system evolves
 

docs/cloud/billing-and-usage/actions-usage.mdx

@@ -0,0 +1,74 @@
+---
+id: actions-usage
+title: Usage dashboards
+sidebar_label: Usage dashboards
+description:
+  Temporal Cloud offers flexible, predictable pricing for Workflows, Activities, Workers, and Storage. Pay for what you
+  use with volume discounts and credit savings.
+slug: /cloud/actions-usage
+toc_max_heading_level: 4
+keywords:
+  - explanation
+  - introduction
+  - pricing
+  - actions
+  - temporal cloud
+  - term
+tags:
+  - Temporal Cloud
+  - Pricing
+  - Actions
+  - Support
+---
+
+import { CaptionedImage } from '@site/src/components';
+
+## Usage {#usage}
+
+Actions usage is tracked across an account in the [usage dashboard](https://cloud.temporal.io/usage) and is visible to
+Account Owners, Finance Admin and Global Admin. For individual Namespaces, usage can be seen in the
+[Namespace summary](https://cloud.temporal.io/namespaces/) for a specific Namespace.
+
+![Temporal Cloud Usage dashboard](/img/cloud/billing/usage-dashboard.png)
+
+## Actions in Workflows {#actions-in-workflows}
+
+When viewing a Workflow history, events that represent a Billable Action are annotated with the number consumed by the
+event in the **Billable Actions** Column. These Actions are summarized at the top of the workflow.
+
+<CaptionedImage
+    src="/img/cloud/billing/aggregate-billable-actions.png"
+    title="Temporal Cloud Usage dashboard showing aggregated Billable Actions"
+/>
+
+<CaptionedImage
+    src="/img/cloud/billing/individual-billable-actions.png"
+    title="Temporal Cloud Usage dashboard showing individual Billable Actions associated with events"
+/>
+
+This Billable Action estimate is useful for projecting the cost of Workflows. For example, if you ran a test Workflow
+that generated 20 Billable Actions and projected that it would be run 100 times a day for a month, you could anticipate
+that Workflow to generate 20 Actions x 100 runs/day x 30 days = 60,000 Billable Actions per month. You can also use the
+Billable Action estimate to help optimize Workflows by better understanding your cost drivers.
+
+:::tip Excluded Billable Actions
+
+The Billable Action estimate is an experimental feature and only measures Billable Actions that exist within Workflow
+event histories. Some billable concepts are not included in these calculations such as:
+
+- Query
+- Activity Heartbeats
+- Rejected Update Workflow Executions
+- Export
+- Schedule
+- Replicated Actions that occur in a
+  [Namespace replication](../../cloud/high-availability/index.mdx#high-availability-features)
+
+Additionally, Workflows with the `TemporalNamespaceDivision` Search Attribute set may not have accurate Billable Action
+Estimates. The estimated Billable Actions should only be treated as an estimate. If billable events exist outside of
+event history, the Actions count could be higher.
+
+:::
+
+[Reach out](https://pages.temporal.io/contact-us) to our team for more information or to help size your number of
+Actions.

docs/cloud/billing-api.mdx …/cloud/billing-and-usage/billing-api.mdxdocs/cloud/billing-api.mdx renamed to docs/cloud/billing-and-usage/billing-api.mdx docs/cloud/billing-api.mdx renamed to docs/cloud/billing-and-usage/billing-api.mdx

@@ -1,10 +1,10 @@
 ---
-id: billing-and-cost
-title: Usage and billing management
-sidebar_label: Usage and billing
+id: billing
+title: Billing Center
+sidebar_label: Billing Center
 sidebar_position: 3
 description: As an Account Owner, you can access and manage billing details anytime, with invoices available for download on the Billing page. Typical billing cycles begin on the first of the month (UTC).
-slug: /cloud/billing-and-cost
+slug: /cloud/billing
 toc_max_heading_level: 4
 keywords:
   - billing
@@ -21,31 +21,7 @@ tags:
   - Temporal Cloud
 ---
 
-import * as Components from '@site/src/components';
 
-Temporal strives to provide full transparency over billing and costs.
-Use this information to assess your spending patterns, inspect your credit ledger, check your invoice histories, update payment details,
-and manage your current plan as needed.
-
-For more information on current Temporal Cloud pricing for Actions, storage, and services/support, please visit our [Pricing](/cloud/pricing) page.
-
-Temporal Provides multiple ways to view your usage and billing data:
-
-- [Billing Center](https://cloud.temporal.io/billing) allows you to see summary invoices and credits, manage plans, and delete your accounts.
-    - Coming soon: Billing dashboard enhancements to visualize billing by Namespace over time
-    - Viewable by Account Owners and Finance Admin
-- [Usage Dashboards](https://cloud.temporal.io/usage) allow you to monitor Namespace level usage over time.
-    - Coming soon: Additional granularity based on Action Types, grouping by Tags, and grouping by Projects
-    - Viewable by Account Owners, Finance Admin, Global Admin on an account level. Namespace level usage is visible on the Namespace pages to those with access.
-- [Billing API](/cloud/billing-api) allow you to access billing information on a Namespace basis down to an hourly granularity, enriched with Tags and Projects.
-The Billing API provides a FOCUS-guided data format that can be ingested into your cloud cost management platform or analytics tooling, or downloaded as a CSV.
-    - Viewable by Account Owners, Finance Admin
-
-:::tip Support, stability, and dependency info
-
-The Temporal Cloud Billing API is in [Pre-release](/evaluate/development-production-features/release-stages#pre-release).
-
-:::
 
 ## Current balance {#current-balance}
 

…s/cloud/get-started/billing-and-cost.mdx docs/cloud/billing-and-usage/billing.mdxdocs/cloud/get-started/billing-and-cost.mdx renamed to docs/cloud/billing-and-usage/billing.mdx docs/cloud/get-started/billing-and-cost.mdx renamed to docs/cloud/billing-and-usage/billing.mdx

@@ -0,0 +1,65 @@
+---
+id: index
+title: Billing and usage management
+sidebar_label: Billing and usage
+sidebar_position: 3
+description: As an Account Owner, you can access and manage billing details anytime, with invoices available for download on the Billing page. Typical billing cycles begin on the first of the month (UTC).
+slug: /cloud/billing-and-usage
+toc_max_heading_level: 4
+keywords:
+  - billing
+  - invoices
+  - cost management
+  - account owner
+  - billing cycle
+  - payment options
+  - credit usage
+  - temporal cloud
+  - account balance
+  - invoice history
+tags:
+  - Temporal Cloud
+---
+
+import * as Components from '@site/src/components';
+
+
+Temporal Cloud provides billing and costs information for your account. 
+Use this information to assess your spending patterns, inspect your credit ledger, 
+check your invoice histories, update payment details, and manage your current plan as needed.
+
+For more information on current Temporal Cloud pricing for Actions, storage, and services/support, 
+please visit our [Pricing page](/cloud/pricing).
+
+Usage on Temporal is measured in Actions and Storage. 
+This can help understand your bills, forecast usage, optimize Workflows, and troubleshoot errors. 
+You can view your Action usage in multiple ways.
+The following tools are available for measuring Usage and Billing:
+
+- **[Billing Center](/cloud/billing):** Allows you to see summary invoices and credits, manage plans, and delete your accounts.
+    - Viewable by Account Owners and Finance Admin
+
+- **[Billing API](/cloud/billing-api):** Allows you to access billing information on a Namespace basis down to an hourly granularity, enriched with Tags and Projects. The Billing API provides a FOCUS-guided data format that can be ingested into your cloud cost management platform or analytics tooling.
+    - Viewable by Account Owners and Finance Admin
+
+:::tip Support, stability, and dependency info
+
+The Temporal Cloud Billing API is in [Pre-release](/evaluate/development-production-features/release-stages#pre-release).
+
+:::
+
+- **[Usage Dashboards](/cloud/actions-usage):** Aggregate Actions on a Namespace level and includes Action categories that groups similar types of Actions as seen in [Actions](/cloud/actions). Available in the Cloud UI in the usage dashboard and Namespace overview pages.
+    - Viewable by Account Owners, Finance Admin, Global Admin on an account level. Namespace level usage is visible on the Namespace pages to those with access.
+
+- **[Actions in Workflow History](/cloud/actions-usage#actions-in-workflows):** Highlights Actions in a given Workflow History via the Temporal Cloud UI. Note that some Actions are not measured in Workflow histories.
+    - Viewable by Account Owners, Global Admin and Namespace Admin, Developers and Read-only
+
+- **[Actions Metrics](/cloud/metrics/openmetrics):** A high cardinality billable action metric that include labels for Category, Action Type, Workflow Type and Namespace down to minute granularity.
+    - Viewable by creating a service account with the "Metrics Read-Only" role. See the [OpenMetrics](/cloud/metrics/openmetrics#api-key-authentication) page for more information.
+
+:::tip Support, stability, and dependency info
+
+Temporal Cloud Action Metrics is in [Public Preview](/evaluate/development-production-features/release-stages#public-preview).
+
+:::
+

docs/cloud/billing-and-usage/index.mdx

@@ -78,7 +78,7 @@ is the time the export uploads to object storage, not the Workflow completion ti
       - Last Status Check: This reflects the timestamp of the latest internal Workflow healthcheck.
 
    - Usage Dashboard:
-      - Actions from the Export Job are included in the [Usage Dashboard](/cloud/billing-and-cost).
+      - Actions from the Export Job are included in the [Usage Dashboard](/cloud/actions-usage).
 
 3. **Metrics**:
    - Export-related metrics are available from the [Cloud metrics endpoint](/cloud/metrics/), specifically the metric `temporal_cloud_v1_total_action_count` with the label `is_background="true"`.

docs/cloud/export.mdx

@@ -39,7 +39,7 @@ To create a Temporal Cloud account, sign up [here](https://temporal.io/get-cloud
   - [Manage Namespaces](/cloud/namespaces)
   - [Manage users](/cloud/users)
   - [Manage user groups](/cloud/user-groups)
-  - [Manage billing](/cloud/billing-and-cost)
+  - [Manage billing](/cloud/billing)
   - [Manage Service Accounts](/cloud/service-accounts)
 - [API key feature guide](/cloud/api-keys)
 - [Metrics feature guide](/cloud/metrics)

docs/cloud/index.mdx

@@ -34,7 +34,7 @@ Standalone Activities are Temporal's [job queue](/evaluate/development-productio
 
 If you need to orchestrate multiple Activities, then you should use a Workflow. But if you just need
 to execute a single Activity, then you can use a Standalone Activity. This will result in fewer
-[Billable Actions](/cloud/actions#actions-in-workflows) in Temporal Cloud than using a Workflow to
+[Billable Actions](/cloud/actions-usage#actions-in-workflows) in Temporal Cloud than using a Workflow to
 run a single Activity. If your Activity Execution is short-lived, then you will also notice lower
 latency, since there are fewer Worker round-trips than when executing the Activity in a Workflow.