- 9 minutes to read

Release Notes

Managing Correlated Events

Investigate incomplete transactions, clear error states, and fine-tune correlation parameters using powerful remote actions—ensure business processes complete successfully and meet SLA requirements.

Take control of your transaction monitoring with the Nodinite Log File Parser Monitoring Agent. On this page, you will:

  • ✅ Investigate incomplete transactions—view detailed error reports with start/end patterns and timeout information
  • ✅ Reset transaction states—clear historical errors and start fresh monitoring cycles
  • ✅ Optimize correlation settings—adjust timeout thresholds and pattern parameters without agent restarts
  • ✅ Analyze transaction patterns—export data for business analysis, SLA reporting, and process improvement

You can perform all management actions through the Nodinite Web Client using Remote Actions on correlated event Resources. This page explains transaction management capabilities. For correlation concepts and setup, see Monitoring Correlated Events.

Available Remote Actions

The Nodinite Web Client provides comprehensive management actions for correlated event monitoring resources:

Investigation Actions

  • [Error Report][#fa-circle-info-error-report] - View incomplete transactions with detailed start/end pattern analysis
  • [Show Log Files][#fa-file-alt-show-log-files] - Display and download monitored transaction log files

Management Actions

  • [Clear Errors][#fa-broom-clear-errors] - Reset transaction states and ignore historical incomplete transactions
  • [Edit Thresholds][#fa-edit-edit-time-based-thresholds] - Adjust timeout values and correlation parameters

Monitoring Actions

  • [View Logs][#fa-file-alt-show-log-files] - Access real-time log content for transaction analysis
  • [Download Files][#fa-download-download-log-files] - Retrieve log files for offline analysis and archiving

Available Remote Actions Menu
Remote Actions available for correlated events monitoring resources in the Web Client

Error Report

View detailed information about incomplete transactions including start patterns, missing end patterns, timeout details, and correlation analysis.

The Error Report provides comprehensive visibility into transaction failures and delays:

Transaction Analysis

  • Incomplete transactions - Show all transactions with start patterns but no corresponding end patterns
  • Timeout details - Display how long transactions have been pending and remaining time before timeout
  • Pattern matching - Show exact start pattern matches and expected end pattern format
  • Correlation IDs - Display extracted transaction identifiers used for correlation tracking

Report Information

  • Transaction timeline - Show when start events were detected and timeout thresholds
  • Pattern context - Display surrounding log content for start pattern matches
  • File locations - Identify which log files contain start events and where end events are expected
  • State summary - Overview of pending, warning, and error transaction counts

Error Report Example
Error Report showing incomplete transaction details with correlation analysis

Business Intelligence

Use Error Report data for:

  • SLA monitoring - Track transaction processing times against business commitments
  • Process optimization - Identify common incomplete transaction patterns for workflow improvement
  • Root cause analysis - Correlate transaction failures with system events, deployments, or load patterns
  • Capacity planning - Analyze transaction volume and processing times for infrastructure scaling

Export Options

  • CSV export - Download transaction data for spreadsheet analysis and reporting
  • Filtered views - Focus on specific transaction types, time periods, or error conditions
  • Scheduled reports - Configure automated error reports for regular business review

Clear Errors

Reset the error state for correlated event monitoring resources and start fresh transaction tracking cycles.

The Clear Errors action removes all currently tracked incomplete transactions and resets resource states:

What Gets Cleared

  • Pending transactions - Remove all transactions currently awaiting end pattern matches
  • Error states - Reset resource status from Error/Warning to OK state
  • Historical timeouts - Clear all previously timed-out transactions from tracking
  • Warning conditions - Remove transactions approaching timeout thresholds

What Stays Protected

  • Configuration settings - All start/end patterns and timeout thresholds remain unchanged
  • Log file content - Original log files are never modified or deleted
  • Future monitoring - Continuous monitoring resumes immediately after clearing errors
  • Archived data - Historical transaction logs in Nodinite database remain for reporting

When to Use Clear Errors

Ideal scenarios:

  • After system maintenance - Clear incomplete transactions caused by planned downtime
  • Configuration changes - Reset states after adjusting correlation patterns or timeouts
  • Business process changes - Clear historical errors when workflows are modified
  • Testing cycles - Reset monitoring after testing incomplete transaction scenarios

Example workflow:

  1. System maintenance causes 50 incomplete payment transactions
  2. Maintenance completes, payment processing resumes normally
  3. Clear Errors removes the 50 incomplete transactions from tracking
  4. Fresh monitoring cycle begins with clean state

Clear Errors Action
Clear Errors dialog confirming reset of transaction states

Show Log Files

Display monitored log files with individual file management, content preview, and download capabilities for transaction analysis.

Access real-time log file content and manage individual files within correlation monitoring:

File Management Features

  • File listing - Display all log files currently being monitored for correlation patterns
  • Content preview - View recent log file content directly in the Web Client
  • Download files - Retrieve log files for offline analysis and archiving
  • File status - Show file sizes, last modified dates, and accessibility status

Multi-File Correlation Support

  • Wildcard patterns - Manage files matched by pattern expressions (payment_*.log)
  • Date rotation - Handle daily/hourly log files with automatic discovery
  • SMB shares - Access network-mounted log files with proper authentication
  • Mixed file types - Display different log formats within the same correlation configuration

Transaction Context

  • Pattern highlighting - Identify lines containing start and end pattern matches
  • Correlation tracking - See which files contain related transaction events
  • Timeline analysis - View transaction sequences across multiple files
  • Context preservation - Maintain original log formatting and structure

Show Log Files Display
Log Files view showing monitored files with content preview and download options

Advanced File Operations

  • Selective download - Download specific files containing relevant transactions
  • Batch operations - Download multiple related log files for comprehensive analysis
  • Archive integration - Export log files with transaction correlation metadata
  • Search capabilities - Find specific transaction IDs or patterns across files

Download Log Files

Retrieve individual or multiple log files for offline analysis, archiving, and detailed transaction investigation.

Download capabilities support comprehensive transaction analysis and compliance requirements:

Download Options

  • Individual files - Download specific log files containing incomplete transactions
  • Batch download - Retrieve multiple related files for complete transaction analysis
  • Compressed archives - Download large log files in compressed format for efficient transfer
  • Filtered content - Export only log entries relevant to specific transaction patterns

Use Cases

  • Forensic analysis - Detailed offline investigation of transaction failures
  • Compliance reporting - Archive log files for regulatory requirements
  • Business analysis - Provide log data to business stakeholders for process improvement
  • Development support - Share log files with development teams for debugging

Download Formats

  • Original format - Preserve exact log file structure and formatting
  • CSV export - Convert transaction data to spreadsheet-friendly format
  • JSON export - Structured data for integration with analysis tools
  • Filtered logs - Export only lines matching correlation patterns

Edit Time-based Thresholds

Adjust timeout values and correlation parameters without restarting the monitoring agent—optimize transaction monitoring for changing business requirements.

Modify correlation settings dynamically to adapt to evolving business processes and SLA requirements:

Threshold Configuration

  • Warning thresholds - Set time limits for generating warning alerts (15 minutes)
  • Error thresholds - Configure maximum time before marking transactions as failed (30 minutes)
  • Grace periods - Account for expected delays during peak processing times
  • Business hours - Apply different thresholds for business vs. after-hours processing

Dynamic Updates

  • No agent restart - Changes take effect immediately without service interruption
  • Active transaction handling - Existing pending transactions adopt new threshold values
  • Validation checks - Ensure warning thresholds are less than error thresholds
  • Configuration backup - Previous settings are preserved for rollback if needed

Business Scenario Examples

E-commerce Order Processing:

  • Normal hours: 2-hour warning, 4-hour error
  • Peak season: 4-hour warning, 8-hour error
  • Weekend processing: 8-hour warning, 24-hour error

Financial Transaction Processing:

  • Real-time payments: 30-second warning, 2-minute error
  • Batch transfers: 10-minute warning, 30-minute error
  • International wires: 2-hour warning, 8-hour error

Edit Thresholds Interface
Edit Thresholds dialog showing warning and error timeout configuration

Advanced Configuration

  • Transaction type differences - Set unique thresholds for different correlation patterns
  • Priority levels - Apply shorter timeouts for high-priority transactions
  • SLA alignment - Configure thresholds to match business service level agreements
  • Performance optimization - Balance monitoring frequency with system resource usage

Performance Optimization

Resource Management

  • Memory efficiency - Clear completed transactions automatically to prevent memory growth
  • CPU optimization - Adjust scan intervals based on transaction volume and urgency
  • Storage optimization - Archive old transaction data while maintaining monitoring performance
  • Network efficiency - Optimize log file access patterns for SMB shares and remote files

Monitoring Tuning

  • Scan frequency - Balance responsiveness with system resource consumption
  • Batch processing - Configure optimal batch sizes for high-volume transaction environments
  • Timeout granularity - Set appropriate timeout check intervals for business requirements
  • Alert frequency - Control notification rates to prevent alert fatigue

Performance recommendations:

  • High-volume environments: Increase scan intervals to 60+ seconds for efficiency
  • Real-time monitoring: Use 10-30 second intervals for immediate transaction visibility
  • Mixed workloads: Configure different scan frequencies per correlation pattern

Security & Access Control

File Access Security

  • SMB authentication - Secure access to network-mounted log files with proper credentials
  • Read-only operations - All remote actions are read-only; original log files never modified
  • Audit trails - Track all remote action executions for compliance and security
  • Role-based access - Control which users can perform specific remote actions

Data Protection

  • Secure downloads - Encrypted file transfers when downloading log files
  • Content filtering - Option to mask sensitive data in log file previews
  • Retention policies - Automatic cleanup of downloaded files based on business requirements
  • Compliance support - Features support GDPR, SOX, and other regulatory requirements

Best Practices

Transaction Management

  1. Regular error review - Check Error Reports daily for incomplete transactions
  2. Proactive threshold tuning - Adjust timeouts based on actual business processing times
  3. Clear errors strategically - Use Clear Errors after maintenance windows or configuration changes
  4. Download critical logs - Archive log files for transactions requiring detailed investigation

Performance Optimization

  1. Monitor resource usage - Track agent memory and CPU consumption during peak transaction periods
  2. Optimize file patterns - Use specific file patterns to reduce unnecessary file scanning
  3. Schedule maintenance - Perform Clear Errors operations during low-traffic periods
  4. Archive old data - Download and archive log files for long-term compliance storage

Business Alignment

  1. Align thresholds with SLAs - Configure timeout values to match business service commitments
  2. Coordinate with stakeholders - Share Error Reports with business teams for process improvement
  3. Plan for peak periods - Adjust thresholds during known high-volume processing times
  4. Document procedures - Maintain runbooks for common transaction management scenarios

Next Steps

Ready to manage your transaction monitoring?

Monitoring Correlated Events - Learn correlation concepts and configuration setup
Configuration - Correlated Events - Set up start/end patterns and timeout thresholds
How to Monitor Correlated Events - Complete step-by-step implementation guide

Need other monitoring approaches?

Monitoring Content Files - Pattern-based content detection and alerting
Managing Content Files - Content-based monitoring management actions

Monitoring Correlated Events - ACK/NAK correlation concepts and transaction tracking
Monitoring Content Files - Pattern-based content detection monitoring
Configuration - Correlated Events - Complete correlation setup guide
Troubleshooting Correlation Monitoring - Common issues and resolution guides