Cloud Cruiser became HPE Consumption Analytics on Nov. 1st. You'll still see the old name in places while we update this site.

 

 

Consumption Analytics Documentation

Home > Cloud Cruiser 3 > Administering > Managing customers > Customer activities and attributes > Setting up budgets and alerts > Alert processing modes

Alert processing modes

Cloud Cruiser is very flexible in its design for customer accounting periods. Any customer in any level of the account structure hierarchy can have a different accounting period. One might start on the 5th of the month and go to the 4th of the next month, while another starts on the 1st and runs to the end of the month, while still another runs from the 15th of one month to the 14th of the next. Therefore, based on the selection date when the alert_process.xml job runs, different accounts could be in different accounting periods.

The alert task can be run two modes: Default and Specific Accounting Period . Each mode handles accounting periods differently.

Default mode

In the Default mode, a database query for every customer that has an alert defined will be executed. First the database is queried for all alert definitions. Then for each definition, the appropriate accounting period is determined (based on the selection date and the customer’s accounting day) and then the database is queried to aggregate the usage for that period for that customer. Alert levels are then checked and the appropriate actions taken.

NOTE: This is the most database intensive mode, but it is also the most precise.

Specific Accounting Period mode

In the Specific Accounting Period mode, the user specifies a specific accounting period and year through the alert_process.xml file. Then one database aggregation query is issued for the specific accounting period, regardless if it is the current customers accounting period (the customer’s accounting day is not used in this mode).

For example, for a specific accounting period, you can have the following:

<property name="accountingYear" value="2012"/>
<property name="accountingPeriod" value="07"/>

NOTE: If you specify an accounting period, any date selection made when running the job will be ignored.

Alert mode comparison example

If you have customers with different accounting periods, the results might not be what you expect. Based on this data

 Customer

 Accounting Day

 A-AA

1

 A-BB

10

 A-CC

14

With a selection date of 7/13/2012, the following processing will occur in Default mode:

  • A-AA will be aggregated for accounting period = 07 and accounting year = 2012 because its accounting day of 1 is less than the current selection date.
  • A-BB will be aggregated for accounting period = 07 and accounting year = 2012 because its accounting day of 10 is less than the current selection date.
  • A-CC will be aggregated for accounting period = 06 and accounting year = 2012, because its accounting day of 14 is greater than the selection date, so its accounting period runs from 6/14/2012 to 7/13/2012, which is in the last period, 06.

With a selection date of 7/13/2012, using an accounting period 07 and accounting year 2012, the following processing will occur in Specific Accounting Period mode:

  • A-AA will be aggregated for accounting period = 07 and accounting year = 2012.
  • A-BB will be aggregated for accounting period = 07 and accounting year = 2012.
  • A-CC will be aggregated for accounting period = 07 and accounting year = 2012, which will return no results, since A-CC still has not reached accounting period 07.

alert_process.xml file

The following default options are typically used in the alert_process.xml file:

 Argument

 Value

 Default

accountingYear

nnnn

N/A. Used for Specific Accounting Period processing mode.

accountingPeriod

nn

N/A. Used for Specific Accounting Period processing mode.

projectedTemplateBody

file_name

projected_alert_body.vm

projectedTemplateSubject

file_name

projected_alert_subject.vm

standardTemplateBody

file_name

standard_alert_body.vm

standardTemplateSubject

file_name

projected_alert_subject.vm

Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.
© Copyright 2018 Hewlett Packard Enterprise Development LP