Event export
The Event Export task allows you to export events that occurred during a specified period using one or all event filters. The Task Log shows each filter that exported the events and the directories to which they were exported.
Note: Before running this task, you must first set up the necessary filters in the Event Filters screen.
Use the following procedure to configure a task template:
-
Go to System Operations > Task Management > Task Templates.
-
Use the dropdown menu to select the Task Type and Task Template. (Click Add to create a new task template. For more information, see Adding task templates.)
-
Configure the Task specific parameters. These parameters are defined after step 5 of this procedure.
-
Configure the Common task template parameters. For more information, see Task template parameters.
-
Click Save.
Task specific parameters:
Time Period
Defines the time span of the data to include in the task for exports, reports, and other tasks. Some common time periods include: Today, Yesterday, Month, Month to Date, Week, Week to Date, Year, and Year to Date.
Start Date
Defines the first day from which to include data in the task.
Tip: Defines the date to start the baseline calculation. Use this parameter to indicate how far back your baseline is needed. Typically, this is the first day of operation or recovery period. If this value is not properly set, it may default to the beginning of time, and Like Days may calculate as far back as historic data is available. This will overwhelm the LikeDayAlgorithmDate table and lead to slower processing.
End Date
Defines the last day from which to include data in the task. To include the full 24 hours of the last day, the task will be scheduled with an adjusted End Date (that is, adding one day to the End Date entered in the task parameter).
Time Zone
Defines the time zone that corresponds to the time period and start/end dates you select in the task template.
-
For Rate Event Report, the time zone format is PacificUS, PacificUSNoDst, and EasternUS.
-
For TOU Schedules, the IDs cannot start with a numeric character. For example, "400_TOUSchedule" is not a valid ID. Instead, name the ID "TOUSchedule_400".
Event Filter
Defines the types of events to export and the file or FTP site where the events will be sent. As events are imported into IEE, they are immediately exported using all enabled event filters. You can also schedule a task to export events using one or all event filters. This field is populated from data in the DeviceEventFilter table.
To create event filters, go to Device Events workbench > Tools > Event Filters, and click Add.
Chunk Size
Defines the number of request items grouped for internal processing in the ADE export service. Affects the number of entities that are retrieved from the AdeEntity database table during configuration fetches and data availability fetches. Affects the number of entities that are retrieved from the database during configuration fetches and data availability fetches.
Chunk size is a parameter common to several task templates. The higher the chunk size value, the greater the portion of the total available work each IEE task runner performs. A smaller value means dividing the work between more concurrent task runners.
Chunk sizes that are too large overburden a few task runners, while other task runners sit idle. In extreme cases, overly large chunk sizes could result in system failure due to lack of available, allocated memory. Chunk sizes that are too small spawn many task runners that perform more initialization and shutdown than actual work. Both large and small extremes will cause delays in export processing.
When fine tuning chunk sizes, consider database resources, hardware requirements, daily processing levels, and processing windows. Adjust values over time, as hardware and networking conditions change.