Usage Configuration Table
Applies To: Windows Azure Pack
The [Usage].[Configuration] table provides various usage configuration settings that can be of use for troubleshooting. It is located in the [Microsoft.MgmtSvc.Usage] schema.
Usage.Configuration
Key |
Default Value |
Description |
|---|---|---|
BatchSize |
10000 |
Batch size used by the collector when asking resource providers for their usage data. |
DefaultProviderQueryDuration |
180000 |
The delay in milliseconds between each request to a resource provider |
ActivePassivePollingInterval |
60000 |
This setting is used in scaled environments as a delay before “passive” instances of the usage collector will attempt to become “active”. |
DataRetentionDurationDays |
40 |
The length of time in days that data in the [usage].[Records] table will be kept before being deleted (a job runs once a day that deletes records older than this amount of days). |
MaintenanceCycleScheduleTime |
03:00:00 |
The time of day at which the aforementioned job runs. It deletes old usage an diagnostic data. |
DiagnosticDataRetentionDays |
3 |
The length of time in days that data in the [UsageDiagnostics].[*] tables will be kept before being deleted (a job runs once a day that deletes records older than this amount of days). |
MaximumBatchSize |
10000 |
The maximum number of usage records that will be returned in a single response to a third party request for usage data from Windows Azure Pack |
OutgoingCallsDefaultTimeoutInSeconds |
120 |
The length of time in seconds to wait for a response from a notification subscriber or resource provider |
SubscribersExpirationIntervalInSeconds |
120 |
The interval in seconds between requests from the usage service to refresh its cached information about notification subscribers. For performance reasons, the usage service does not read notification subscriber changes in the database as they are made. Instead the database is contacted once every SubscribersExpirationIntervalinSeconds in order to refresh the cached information. Restarting the usage service will cause the cached data to refresh immediately. |
See Also
Windows Azure Pack Usage Service
Troubleshooting the Windows Azure Pack Usage Service