How to monitor Firebird server activity?

- Firebird 2.5 and above provides full Audit and Trace capability
- Firebird 2.1 and above provides monitoring tables
- for earlier versions you can use some 3rd-party applications

Firebird 2.5 has a complete Audit and Trace Services API, which allows you to monitor database activity continuously. More information on this monitoring approach is available in Firebird 2.5 Release Notes and the following article:

Firebird 2.1 and above features server-side monitoring via special system tables. This way you can monitor your server by using SQL statements. Those system tables all have prefix MON$ in their name. To use them, you need to make sure your database file is created with Firebird 2.1 or higher (ODS version 11.1). If you have a database that is created with earlier versions, you need to do backup and subsequent restore with Firebird 2.1 to have those tables.

For detailed information about each monitoring table, read the file README.monitoring_tables in 'doc' directory of your Firebird installation.

Please note that monitoring tables just offer the data, but you'll probably need some way to aggregate those and spot the problems. A tool that does this well is Sinatica Monitor:

Do you find this FAQ incorrect or incomplete? Please e-mail us what
needs to be changed. To ensure quality, each change is checked by our editors (and often tested on live Firebird
databases), before it enters the main FAQ database. If you desire so, the
changes will be credited to your name. To learn more, visit our add content page.

If you are a commercial tool maker and your tool features a great way to handle
the issue written about in this FAQ, please check out our advertisement page.