Enterprise RTView® 
User Guide

Archiving Data

NOTE: You may not be licensed to run all Enterprise RTView data sources.

With the Historian you can archive data from any Enterprise RTView data source to any database using JDBC. The Historian is a separate application process that runs independently from the other RTView data servers. The sole purpose of the Historian is to gather data and then, optionally, process that data and store time-stamped values in your database. This historical information is most often utilized as a source of data (via SQL data attachments) in dashboards and alert definitions in RTView solutions.

Use Cases for Historical Data
 

  Analysis   Baseline   Reporting and Audit Trails
  • Keep an archive of metrics so that a trend chart can display a wide range of metric values over a long period of time
  • Compare current values with historical values in a dashboard
  • Keep a history of a particular metric over a period of time so that alert rules can be created which might indicate that a current real-time metric is x% out of normal range, rather than hard-coding threshold boundaries
  • Provide a database that other reporting or auditing tools can use to survey your historical metrics

The Historian uses files created with the Display Builder to determine what data to archive. These Data Configuration (.rtv) files specify how to access the data and perform required transformations in the data. The Historian is then configured to create connections to the necessary data sources and uses the Data Configuration (.rtv) files you specify to determine what data to archive from those sources. Once started, the Historian will gather the data as defined and place the time-stamped information into the designated tables.

It is possible to install multiple versions of the Historian (to segment data collection into different databases) and to configure the Historian to be fault-tolerant. There are default schemas for the Historian, but the configuration of the database schema is largely configurable. For example, you can use configuration files to identify your own table names and, if you choose, the Historian will create those tables in your database if they do not already exist.

 

 
Enterprise RTView contains components licensed under the Apache License Version 2.0.

 

Treemap Algorithms v1.0  is used without modifications and licensed by MPL Version 1.1. Copyright © 2001 University of Maryland, College Park, MD

 

Datejs is licensed under MIT. Copyright © Coolite Inc.

 

JCalendar 1.3.2 is licensed under LGPL. Copyright © Kai Toedter.

 

jQuery is licensed under MIT. Copyright © John Resig,

 
JMS, JMX and Java are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. They are mentioned in this document for identification purposes only. 

 
SL, SL-GMS, GMS, Enterprise RTView, SL Corporation, and the SL logo are trademarks or registered trademarks of Sherrill-Lubinski Corporation in the United States and other countries. Copyright © 1998-2009 Sherrill-Lubinski Corporation. All Rights Reserved.