- 7 minutes to read

Release Notes

Managing Correlated Events

Perform remote actions on transaction correlation monitoring resources—adjust timeout thresholds, investigate incomplete transactions, clear error states, and download transaction log files without server access.

What are Managing Actions?

Remote management actions allow you to control correlated event monitoring resources directly from the Nodinite Web Client. Adjust SLA thresholds, review incomplete transactions (ACK without NAK), reset alert states, and access transaction log files—all without logging into servers.

Why Use Remote Actions?

  • No server access required - Manage monitoring configurations from your browser, no RDP or SSH needed
  • Real-time adjustments - Change timeout thresholds instantly to match business requirements without agent restart
  • Transaction visibility - View pending transactions awaiting completion with full correlation context
  • Team collaboration - Enable non-technical staff to investigate transaction delays via role-based access control
  • Audit compliance - All actions logged to Audit Trail for regulatory and governance requirements

When to Use These Actions?

  • Business SLA changes - Adjust warning/error timeouts when processing times change (peak season, new partners, system upgrades)
  • Transaction investigations - Review which transactions are incomplete and why (start event detected, end event missing)
  • Post-maintenance cleanup - Clear pending transaction alerts after planned downtime or system restarts
  • Root cause analysis - Download transaction log files for offline investigation or sharing with development teams

Each correlated events configuration appears as a Resource in Nodinite Monitor Views.

Tip

To understand correlation concepts and configuration, see Monitoring Correlated Events.

Available Remote Actions

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

  • Edit Thresholds - Adjust timeout values and correlation parameters
  • Error Report - View incomplete transactions with detailed start/end pattern analysis
  • Clear Errors - Reset transaction states and ignore historical incomplete transactions
  • Show Log Files - Display and download monitored transaction log files

Edit Time-based Thresholds

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

Edit Thresholds Action
Edit thresholds menu option in the Actions button

Threshold Configuration

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

  • Warning thresholds - Set time limits for generating warning alerts (e.g., 15 minutes)
  • Error thresholds - Configure maximum time before marking transactions as failed (e.g., 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

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

Error Report

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

Show Error Report Action
Error Report menu item in the Actions button

Transaction Analysis

Error Report Example
Error Report showing incomplete transaction details with correlation 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

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

  • Download files - Save individual log files or create ZIP archives of all transaction logs
  • CSV export - Download transaction data for spreadsheet analysis and reporting
  • Filtered views - Focus on specific transaction types, time periods, or error conditions

Clear Errors

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

Clear Errors Action
Clear Errors menu option in the Actions button

Confirmation Dialog

You must confirm intent to clear errors before the action is executed:

Clear Errors Confirmation
Clear Errors confirmation dialog requesting user confirmation

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

  • 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

Success Confirmation

If the operation is successful, a confirmation message is displayed:

Clear Errors Success
Clear Errors success message confirming transaction states have been reset

Show Log Files

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

Show Log Files Action
Show Log Files menu option in the Actions button

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

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

Next Steps

Working with existing correlation monitoring?

Adjust Timeouts - Fine-tune SLA thresholds
View Error Reports - Investigate incomplete transactions
Clear Transaction States - Reset monitoring after investigating issues

Need to set up new correlation?

Monitoring Correlated Events - Understand transaction correlation concepts
Configuration - Correlated Events - Set up start/end patterns