2. Logging and observability

This guide consolidates how the Connector logs processes and how to use those signals operationally.

2.1. Core logging tables

• MFProcessBatch — high-level processes (start/completion, duration).

• MFProcessBatchDetail — step-level details across a process batch.

• MFUpdateHistory — XML snapshots of object versions and changes.

• MFLog — errors and operational messages.

2.2. Execution logging model

All standard procedures write to the MFProcessBatch and MFProcessBatchDetail tables. A typical pattern is:

1. Open a process batch using spMFProcessBatch_Upsert (LogStatus “Start”).

2. Log significant steps using spMFProcessBatchDetail_Insert with the same ProcessBatch_ID.

3. Close the batch using spMFProcessBatch_Upsert (LogStatus “Completed”).

Custom procedures should follow the same pattern to ensure a single, correlated view of operations.

2.3. How-to topics

• Logging execution of Process and Procedure Steps

• Logging in custom procedures

• Error tracing

• MFUpdateHistory for logging of class record changes

2.4. Operational checks

• Recent processes: select latest rows from MFProcessBatch; drill into MFProcessBatchDetail for a given ProcessBatch_ID.

• Performance: spMFGetProcedurePerformance produces analytics for a chosen ProcessBatch_ID.

• Context menu actions: VAF creates and completes batches automatically; details appear in both process tables.

2.5. Configuration switch

MFSettings contains the ‘App_DetailLogging’ switch (default 0). Set to 1 to write detailed logs to MFProcessBatch and MFProcessBatchDetail.

2.6. Related references

• Logging Tables

• Enabling and configuring the VAF logging