Database Monitoring
With the newly added per-database capabilities in FB TraceManager V2.5.0, you now have an extended and integrated toolset beyond the already available Audit and Trace Services API support. The following additional per-database monitoring facilities are now available:
• | Header Page Monitoring |
• | Monitoring (MON$) Tables integration |
Combined with the continuous monitoring capabilities of the Firebird Trace API, you are now able to monitor, trace and inspect your database from different aspects. This allows you to identify potential bottlenecks and to improve and tune your server/database configuration. We've tried to make this new monitoring facilities easy to use, especially with a customizable color management facility, which allows you to spot suspicious database operations and settings more easily. For example:
• | When Forced Writes is set to OFF |
• | When no space on the database page is reserved for back record versions |
• | When the sweep interval is set to 0, so that you need to schedule a manual sweep e.g. every night |
• | When the database is shutdown and in which shutdown mode |
• | When the gap of the transaction counters exceed a certain threshold |
• | When the cache hit ratio [%] is below a certain threshold |
• | To identify the oldest active transaction |
• | Did garbage collection happen |
• | And much more ... |
This is a lot of useful information beside monitoring your server/database with the Trace API, to optimize your Firebird environment even further.
See also
Database Monitoring - Header Page Monitoring
Database Monitoring - Monitoring (MON$) Tables