You can add log queries to any C++, C#, VB.NET, Java or Delphi application that you are writing.

	New Feature in Iguana 4.1 This log query capability is new in Iguana 4.1. You can use log queries to, for example, customize error notifications and generate reconciliation reports.

To include a log query, define an object of type LogQuery, supply it with information about the query you want to perform, and then execute the query. An object of type LogQueryResult is returned, which contains the results of the query.

For more details on the LogQuery and LogQueryResult objects, see the language-specific documentation for the log query API:

• C++: CHM, CHMnet and IGC Libraries Data Structures
• C# or VB.NET: iNTERFACEWARE.Iguana.Plugin Namespace
• Java: Overview (iNTERFACEWARE Java Stubcode) (click the link to the com.interfaceware.iguana.plugin package)
• Delphi: IGC Iguana Plugin Package

To include log queries in your application, it will need to reference the IGC dynamic library, which includes definitions of the LogQuery and LogQueryResult objects. This is the library that plugins reference. For more information on referencing the IGC dynamic library, refer to one of the following pages, depending on the programming language that you are using:

• Using the IGC Libraries and API in C++
• Using the IGC Libraries and API in VB.NET and C#
• Using the IGC Libraries and API in Java
• Using the IGC Libraries and API in Delphi

When you use the log query API to obtain a list of log messages, the log messages are returned as LogMessage objects. Each LogMessage object represents an individual Iguana log message, and contains a message log ID field that uniquely identifies this message. If you store this message log ID in a database table, you can use it to obtain a direct link to the Iguana log entry for the message. For more details on how to use the message log ID, see Using the Message Log ID in VMD Files.

	When you execute a log query, your program is blocked from continuing further execution until the log query is finished. This means that if you perform a log query from a plugin, the speed at which messages are processed by the channel in which the plugin is running may be adversely affected.

	To achieve better system performance when performing a log query from an application, do the following: Include the log query in a separate program thread. Instead of doing one large query to search your entire log, perform several smaller queries, each with its own date range, and ensure that all dates are included in exactly one of these date ranges. Because all dates are included in exactly one date range, you can combine the results of the separate queries to obtain complete information from the logs.

The following sections describe examples of how you can use the log query API: