Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Ui text box
sizemedium
typeinfo

This post applies only to customers with on-premise installation of interworks.cloud platform

Excerpt
For collecting in daily basis the Azure usage data, we have implemented the Azure Usages Update Controller service. This service is deployed during installation in the following location:

Default LocationC:\Program Files (x86)\Interworks\Cloud360.Setup.AzureUsagesUpdateController
Configuration FileCloud360.Services.AzureUsagesUpdate.exe.config

 

The configuration file is of the following form:

<appSettings>
<add key="StartHour" value="10" />
<add key="StartTime" value="00" />
<add key="Interval" value="12" />
<!--the Interval is in hours-->
<add key="IDUser" value="2" />
<add key="Username" value="admin" />
</appSettings>

How often this service will run for collecting the usage data, depends on Interval parameter and the start time as defined from the parameters StartHour and StartTime.
In the above paradigm the service will run twice the day at 10:00 and 22:00 o'clock. If we want the service to run more often, you need to decrease the interval. If for example the Interval was every 6 hours, the service would run 10:00, 16:00, 22:00 and 04:00 o'clock.

Ui text box
sizemedium
typetip

Make sure that the usages collection service will run before before the Billing Service

Since the collected usage data will be billed from the billing service, you must make sure that the collection service will run before the Billing Services. A safe interval is to run one hour before the Billing Service. Check the page Cloud Platform Window Services for understanding how you will setup when the Billing Service runs.