ExtremeCloud IQ Agent Logging Enhancements

The ExtremeCloud IQ Agent logging feature uses in-memory, buffer-based logging as the default mechanism instead of continuous on-disk file logging. This reduces storage consumption and improves operational efficiency.

Issue: ExtremeCloud IQ Agent records diagnostic logs to on-disk files with continuous logging during normal operation, even when no troubleshooting is in progress. This continuous disk logging consumes switch storage resources and makes real-time diagnostics difficult without manual file management.

Resolution: The logging feature makes buffer-based, in-memory logging the default. Recent diagnostic logs for both the Python ExtremeCloud IQ Agent application and the HiveAgent process are stored in EMS trace buffers that users can access directly from the CLI and view through show tech-support output. File-based, on-disk logging is disabled by default and available only as an on-demand debug-mode facility for extended troubleshooting sessions.

Key Capabilities:

• The ExtremeCloud IQ Agent process uses in-memory buffer-based logging with separate buffers for the Python application and the HiveAgent process
• File-based logging is suppressed by default, eliminating storage consumption for routine diagnostic operations
• Buffer logs are included in show tech-support output for support escalations and diagnostics
• File-based logging is available on demand at critical, error, warning, info, and debug severity levels using the debug CLI for targeted troubleshooting sessions
• Disabling file-based logging stops new writes but preserves previously captured on-disk log files
• The feature is backward compatible with older packages that do not support this logging control; the debug commands are accepted but do not change logging behavior

Behavior Change

After upgrading, ExtremeCloud IQ Agent file-based, on-disk logging is off by default, so the switch does not write new entries to on-disk log files. Any existing log files present on the switch at the time of upgrade are preserved and are not deleted or truncated. Recent activity remains available through the buffer-based trace feature. To resume or extend on-disk file-based logging during a troubleshooting session, enable file-based logging using the debug CLI.