Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS
Configure the visualization data service
The visualization data service logs historic data in text files for reuse with other charting programs. Historic data is logged in comma-separated values with time stamps in standard long value from the java.util.Date class. By using the visualization data service, you can log historical data, calculate charge back values, or perform capacity planning.
Before you begin
You must use the deployment manager to implement this feature. Ensure that if you are using multiple core groups, they are correctly bridgedIf you are a user with either a monitor or an operator administrative role, then you can only view the visualization data service information. If you have a configurator administrative role, then you can change the configuration. If you have an administrator role, then you have all the privileges for the visualization data service.
Procedure
- In the administrative console, click System administration > Visualization data service.
- Select Enable log to start logging historic data.
- Enter a value in the Time stamp format field. The time stamp format specifies a time and date pattern that is used when logging the visualization data. Use the SimpleDateFormat Java class to format your time stamp. For example, to output the 12.06.2006 5:26:30:978 PM PDT timestamp, use the following time stamp format value:
MM.dd.yyyy hh:mm:ss:SSS aaa zIf you are using IBM Tivoli Usage and Accounting Manager, then use a format that separates the date and time into different fields:'MM.dd.yyy, hh:mm:ss:SSS' 'yyyy.MMMMM.dd, hh:mm:ss'You can also specify the time stamp format with the wsadmin tool:wsadmin.sh -lang jython wsadmin>> vds = AdminConfig.getid("/Cell:OpsManTestCell/VisualizationDataService:/") wsadmin>> vdl = AdminConfig.showAttribute(vds,"visualizationDataLog") wsadmin>> AdminConfig.modify(vdl,[["timestampFormat","MM.dd.yyyy hh:mm:ss:SSS aaa z"]]) wsadmin>> print AdminConfig.show(vdl) wsadmin>> AdminConfig.save()- In the Maximum file size field, type a whole integer for the maximum file size for logs.
- In the Maximum number of historical files field, type a whole integer for the maximum number of logs to be generated per historic cache type.
- In the File name field, type the path where the log files are generated. You can use a variable in the file name value, for example: ${LOG_ROOT}/visualization.
- In the Data log write interval field, type a whole number between 1 and 365 for the interval in which the logs are generated in seconds, minutes, hours, or days.
- From the Data transformer action list, select Average or Skip to specify how to transform data when the interval reaches its maximum value. More data points are provided than you might want to use. The AVERAGE option averages the existing data points between the specified interval, and the SKIP option skips the data points to only use the points specifically at the intervals.
Results
Operational data is exported to the file name that you specified.
What to do next
Now that you have configured the visualization data service, you can import data into an external charting program.
Related tasks
Monitor operations
Related reference
Logs
Administrative roles and privileges