Db2 Log Analysis Tool provides comprehensive log-based solutions on reporting, auditing, recovery and replication. Now there is an additional way of presenting and analyzing the log data in analytics dashboards. This blog looks at a new feature of streaming log summary data to OMEGAMON Data Provider by Log Analysis Tool 3.6 with PTF PH64626.
Log Analysis Tool Summary report shows the number of INSERTs, UPDATEs, and DELETEs per Db2 table (accumulated at the tablespace and database level as well) during the specified time period. Below is the summary batch report: 
Now the new option ‘Send data to ODP’ is available in the classic General Report panel. Enable this option allows summary report data to be streamed into the ODP pipeline.
The following step specifies the ODP Data Broker information (Broker name, Store name, load library), and optionally sets the threshold time to group the data into certain time periods (e.g., every 30 minutes).
Broker name and the Store name will depend on the type of server when Configuring OMEGAMON Data Broker. Data Broker receives data from Log Analysis Tool and stores data in data store, then forwards the data to Sink (OMEGAMON Data Connect). Data Connect transforms data to be sent via JSON to analytics servers like Elastic, Splunk, Kafka, and more. For further OMEGAMON Data Provider information, see here.
To get started quickly, Elastic Kibana dashboards are available on GitHub, you can download it as a starting point and develop your own dashboards. Here are some samples:
Summary of Insert/Update/Delete activity by Db2 Subsystem
By tracking data changes on Db2 subsystem level, you can easily compare data modification activities across different Db2 subsystems. It could also help with proactive planning on the log file sizing, archiving/checkpoint frequency, OUTBUFF setting... for the ‘heavy data changing’ Db2, to prevent potential log performance issues.
Summary of Insert/Update/Delete activity by database
Summary of Insert/Update/Delete activity by object
By viewing data change activity on object level, it is useful for showing how often sensitive objects are updated. If abnormal quantity is shown compared to usual, then you can take a Detail report or use Audit mode to find out the root cause of the unexpected changes.
You can also identify changes over time to see which objects are "hot" (frequently modified), that may require a REORG. When scheduling the REORG utility or other maintenance tasks, you may want to choose a common ‘quiet’ time window with less activities happening by gaining insight from the dashboards, to minimize the impact while saving costs.