All Products
Search

This Product

    ApsaraMQ for RocketMQ:Split bill rules and best practices

    Document Center

    ApsaraMQ for RocketMQ:Split bill rules and best practices

    Last Updated:Mar 10, 2026

    When multiple departments or projects share a single Alibaba Cloud account, tracking per-team costs becomes difficult. ApsaraMQ for RocketMQ integrates with the tag feature in Alibaba Cloud Resource Management, enabling you to tag instances by department, project, or cost center and then filter bills by those tags for accurate cost allocation.

    Supported scope

    Dimension Details
    Editions Pay-as-you-go bills for Standard Edition instances and subscription bills for Platinum Edition instances (ApsaraMQ for RocketMQ 4.0)
    Granularity Instance-level. To isolate costs between departments or applications, use separate instances.
    Mechanism Tag-based. Attach tags to instances, then filter bills by those tags in the billing console.

    Best practices

    Scenario

    A company runs multiple ApsaraMQ for RocketMQ instances under a single Alibaba Cloud account. The finance team needs to break down messaging costs by cost center, department, and project so each business unit sees only the charges it incurs.

    To achieve this, plan your tags, attach them to instances, and then view the split bills.

    Step 1: Plan tags

    Before tagging any resources, decide on a tagging scheme that reflects your organizational structure. A well-designed scheme makes cost reports immediately useful without post-processing.

    The following table shows a sample three-dimension scheme. Adapt it to your organizational structure.

    Dimension Sample tags (key:value)
    Cost center costcenter:Beijing, costcenter:Shanghai, costcenter:Hangzhou
    Department department:Order, department:Shop, department:Item
    Project project:project A, project:project B

    Tag planning tips:

    • Keep keys lowercase and consistent. Inconsistent casing (such as CostCenter vs. costcenter) can cause confusion in reports.

    • Define a mandatory set of tags. At minimum, tag every instance with a cost center and an owner to ensure complete cost attribution.

    • Avoid sensitive data in tag values. Tags appear in billing reports and API responses. Do not use internal budget amounts, employee IDs, or other confidential information as tag values.

    Step 2: Attach tags to instances

    After you finalize your tagging scheme, attach the tags to each ApsaraMQ for RocketMQ instance.

    Example: Instance 1 belongs to Team A of the order department in the Shanghai cost center. Attach all three tags:

    • costcenter:Shanghai

    • department:Order

    • project:project A

    ApsaraMQ for RocketMQ supports two methods for attaching tags:

    Method When to use Reference
    Console Quick, one-off tagging for a small number of instances Add tags
    API Batch tagging or automated tagging in CI/CD pipelines TagResources

    Step 3: View split bills

    Note

    After you attach tags to an instance, split bills reflect the change on the next day (T+1).

    1. Log on to the Expenses and Costs console.

    2. In the left-side navigation pane, choose Costs > Cost Allocation > Split Bill Details.

    3. Filter the bill by tag to view costs for specific dimensions.

    Example 1 -- View costs by cost center:

    In the bill list, select costcenter from the Instance Tag column. The bill displays a separate row for each cost center value (Beijing, Shanghai, Hangzhou).

    Example 2 -- View costs for a specific department and project:

    In the Instance Tags column, select department > Order and project > project A. The bill displays only the charges attributed to the order department's Project A.