Event Log Reporting

Purpose

Explain how to extract, filter, and analyze the M-Files event log data exposed through the connector’s reporting module.

Key Concepts

Event Source

Origin system or component generating the event (e.g. VaultApp, SQL Procedure).

Event Type

Categorization (info, warning, error) enabling targeted filtering.

Process Batch ID

Correlates groups of related operations for performance and auditing.

Object / Class Context

Links an event to specific object metadata (ObjID, Class ID) where applicable.

Usage Examples

Basic extraction:

SELECT TOP 100 *
FROM MFEventLog
ORDER BY EventDate DESC;

Filter errors in last 24h:

SELECT * FROM MFEventLog
WHERE EventType = 'Error'
        AND EventDate >= DATEADD(day,-1, SYSUTCDATETIME());

Aggregate by type:

SELECT EventType, COUNT(*) AS Cnt
FROM MFEventLog
WHERE EventDate >= DATEADD(day,-7, SYSUTCDATETIME())
GROUP BY EventType
ORDER BY Cnt DESC;

Next Steps

  • Add cross-link to performance & optimization once that section is expanded.

  • Include troubleshooting scenarios for common error signatures.