Administer > Policies > Database Policies (Events, Metrics, and Generic Output)

Database Policies (Events, Metrics, and Generic Output)

Database policies enable you to collect data from database tables used by third-party systems by performing a query through a JDBC connection.

The following are examples of data that can be integrated into OMi using database policies:

  • Events from monitoring applications event tables or views.

  • Data from monitoring applications metrics tables.

  • Generic output data from monitoring applications tables.

What data is forwarded

Database policies use a user defined SQL query, an initial value statement, and a static initial value (session variable). The query you provide is used to define a search criterion on the database and with the initial value statement and a set up session variable, you can provide initial values that you can use in filtering. Starting with OMi 10.00, you are no longer limited to a fixed set of SQL clauses but can write more complex queries as well.

For example, if you fetch a field that contains a time stamp, you can write an SQL query to process only data records that happened after the policy was activated. You can do so by setting an appropriate initial value statement that is executed when the policy is activated and then compare the values retrieved in the main SQL clause against this initial value. For details on how the queries are used to fetch and filter records, see Understanding How Data From an SQL Query is Processed topic.

You use defaults and rules to control the data that is sent from Operations Connector to OMi.

Related topics

Understanding How Data From an SQL Query is Processed

How to Export Policies