Megosztás a következőn keresztül:


ConsumptionBudgetData Class

Definition

A class representing the ConsumptionBudget data model. A budget resource.

public class ConsumptionBudgetData : Azure.ResourceManager.Models.ResourceData
type ConsumptionBudgetData = class
    inherit ResourceData
Public Class ConsumptionBudgetData
Inherits ResourceData
Inheritance
ConsumptionBudgetData

Constructors

ConsumptionBudgetData()

Initializes a new instance of ConsumptionBudgetData.

Properties

Amount

The total amount of cost to track with the budget.

Category

The category of the budget, whether the budget tracks cost or usage.

CurrentSpend

The current amount of cost which is being tracked for a budget.

ETag

eTag of the resource. To handle concurrent update scenario, this field will be used to determine whether the user is updating the latest version or not.

Filter

May be used to filter budgets by user-specified dimensions and/or tags.

ForecastSpend

The forecasted cost which is being tracked for a budget.

Id

Fully qualified resource ID for the resource. Ex - /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/{resourceProviderNamespace}/{resourceType}/{resourceName}.

(Inherited from ResourceData)
Name

The name of the resource.

(Inherited from ResourceData)
Notifications

Dictionary of notifications associated with the budget. Budget can have up to five notifications.

ResourceType

The type of the resource. E.g. "Microsoft.Compute/virtualMachines" or "Microsoft.Storage/storageAccounts".

(Inherited from ResourceData)
SystemData

Azure Resource Manager metadata containing createdBy and modifiedBy information.

(Inherited from ResourceData)
TimeGrain

The time covered by a budget. Tracking of the amount will be reset based on the time grain. BillingMonth, BillingQuarter, and BillingAnnual are only supported by WD customers.

TimePeriod

Has start and end date of the budget. The start date must be first of the month and should be less than the end date. Budget start date must be on or after June 1, 2017. Future start date should not be more than twelve months. Past start date should be selected within the timegrain period. There are no restrictions on the end date.

Applies to