As part of the Data Modeling process, required components are identified based on the data source and calculation requirements.
Following is a list of the components that should be identified in the Data Modeling process and their definitions.
|
Event name |
Name of Event as it appears in CA Business Service Insight; should be as descriptive as possible. |
|
Event Behavior |
Behavior of specified Event; when received from the data source, what conditions, and so on. |
|
Timestamp field |
Field in data source used as Event Timestamp. |
|
Event type field |
Field in data source to be translated into an Event type, describing type of reporting. Important that number of different Event Types are minimized as far as possible because Event Type definition is manual and should ideally only be done once. |
|
Data fields |
Fields in data source to be retrieved as data fields. |
|
Resource field |
Field in data source to be translated into a Resource. Contains an entity required to report on with a relatively fixed life. Resource is an entity with a defined life-cycle, where changes can be managed dynamically within the system. Referring to a resource life cycle indicates how frequently new resources are added and changed in allocation to different Service or any other entity of allocation, as mentioned above. The field to be translated as a resource in CA Business Service Insight should have few allocation changes and limited other ones. |
And lastly, based on all of the above definitions:
|
Registration by |
Defines registration criterion. Registration criterion defines Event Type and Resource the Metric registers. Request for Resources can be done directly by registering by Resource, or by allocation entity, such as Service, Contract party, Resource group, Resource type, and so on. This definition is determined by registration capabilities. Another method is Register by Metric, where the current Metric obtains outputs (service level result) from another Metric and use them as input. Possible also to use result from multiple Metrics as input. |
|
Copyright © 2013 CA.
All rights reserved.
|
|