Note: Diagnostics versions 19.05 or newer require Storage Fabric version 19.05 or newer, and vice versa. Combining with an older version is possible only with manually customized /etc/flashgrid-diags.cfg
Note: Diagnostics versions 18.10 or newer require Storage Fabric version 18.10 or newer, and vice versa. Combining with an older version is possible only with Diagnostics email alerts explicitly disabled in /etc/flashgrid-diags.cfg
Version 24.09
New Features: None
Bug Fixes:
- Node monitor fails with missing /var/run/audispd_events #4275
Version 24.05
New Features:
- improve network heartbeat missing message in node_monitor #4172
- collect add-node/remove-node logs in diags #4020
Bug Fixes:
- node-monitor service restarts during deployment #4045
Version 24.01
New Features:
- Update 24.1.65: node update insufficient logging #3087
- Add crsctl stat res -p output to diags #3965
- improve clocks handling on RH8/OL8 in disk latency monitoring #3938
- Alerting on unexpected node reboots #3918
- Provide more data to troubleshoot partially gathered diags #3537
- Add to diagnostics collection: uptime, last, lsblk #3104
Bug Fixes:
- Update 24.1.78: expired policy in flashgrid-diags upload #4038
- on RH7/OL7 do rounding of latencies to significant figures #3946
- incorrect error message when stopping node_monitor service #3941
Version 23.11
New Features:
- update Azure metadata version used by diags #3883
Bug Fixes:
- Update 23.11.139: expired policy in flashgrid-diags upload #4038
- Update 23.11.64: false disk latencies on RH7/OL7 on all disks and growing over time #3928
Version 23.09
New Features:
- Gather sar data in machine readable format #3735
- Collect Azure physical host id in diags #3468
Bug Fixes:
- Update 23.9.200: expired policy in flashgrid-diags upload #4038
- Update 23.9.125: false disk latencies on RH7/OL7 on all disks and growing over time #3928
- false extreme disk latencies logged by node monitor #3638
Version 23.06
New Features: None
Bug Fixes:
- Update 23.6.292: expired policy in flashgrid-diags upload #4038
- node monitor does not log i/o latencies for some non-ASM disks #3607
Version 23.04
New Features:
-
reduce frequency of network monitoring listener restarts #3521
Bug Fixes:
- Update 23.4.353: expired policy in flashgrid-diags upload #4038
- Update 23.4.45: node monitor error when modifying a protected config file #3569
- Update 23.4.21: diags upload failing because of duplicate 'exclude' parameter in /etc/yum.conf file #3548
- License NOT AVAILABLE in alerts #3529
-
correct warning in network monitoring #3520
-
network monitor assumes one cluster per network segment #3487
Version 23.02
New Features:
-
Update 23.2.62: Collect AWS AZ IDs in the diags #3522
-
Capture V$ASM_OPERATION in Diags #3459
Bug Fixes:
- Update 23.2.412: expired policy in flashgrid-diags upload #4038
- Update 23.2.104: node monitor error when modifying a protected config file #3569
- Update 23.2.80: diags upload failing because of duplicate 'exclude' parameter in /etc/yum.conf file #3548
- Update 23.2.71: License NOT AVAILABLE in alerts #3529
-
Update 23.2.62: error in monitoring during low memory condition #3523
Version 22.12
New Features:
- remove color formatting from all logs and utils output #3308
- debug_pack.log improve diagnostics #3045
Bug Fixes:
- Update 22.12.474: expired policy in flashgrid-diags upload #4038
- Update 23.2.37: misleading warning about network monitoring "restarted" #3475
- journalctl not capturing recent events #3370
Version 22.09
New Features:
- add sqlnet.ora file to diags collection #3153
Bug Fixes:
- Update 22.9.565: expired policy in flashgrid-diags upload #4038
Version 22.06
New Features:
- added kernel taint check #3084
Bug Fixes:
- Update 22.6.657: expired policy in flashgrid-diags upload #4038
- DIAGS: The extracting of the DIAGS file changes the owner of the current directory #3105
- info about Azure AZs missing in diags #3081
Version 22.03
New Features:
- Update 22.3.98: reduce min memory alerts threshold #3077
- collect diags via direct SSH in addition to CLAN connection #2962
- automatic DB_BASE detection instead of PATH_DB_BASE parameter in flashgrid_debug_env #2910
- Add config option to issue alerts when peer is not reachable #2887
- add /etc/flashgrid_launcher.cfg to diags #2869
- capture azure disk type in diags #2788
Version 21.09
New features:
- allow disabling ReadLocal #2712
Bug fixes:
- Incorrect entry in flashgrid.rules for auditd #2718
Version 21.08
New features: none
Bug fixes:
- reduce number of captured Listener log files in diags #2662
- flashgrid-diags does not honor TMPDIR #2633
- RHEL8/OL8: Node monitor doesn't report any alerts about system files modification. #2598
Version 21.06
New features:
- RHEL8 / OL8 and Python3 support #2464
- Add /etc/flashgrid-health-check.cfg to Diags #2514
- Capture additional Azure Storage Metadata in diags #2275
- Capture Clusterware Rolling State in diags #2276
- Update 21.6.66: Listener Log Files in Diags #2662
Bug fixes: None
Version 21.02
New features:
- Add FlashGrid license file to Diagnistics Software
- Set licensee name for FlashGrid license
Bug fixes:
- Update 21.2.16: reading EC2 metadata fails when MetadataOptions.HttpTokens set to required #2401
- Update 21.2.1: "No License" message in customer alerts #2300
Version 20.09
New features:
- Compatibility with Health Checker 20.09 #2196
Bug fixes:
- Update 20.9.109: check for availability of sudo permissions #2313
Version 20.02
New features:
- add Health Checker output #1981
- add kernel taint alerts #2022
- cut files of >100MB size when collecting diags #1983
- monitoring free space on / and /u01 #1937
- replace STAP probe with eBPF #1959
Bug fixes:
- Update 20.2.213: Adding waagent.log to Diags Collection on Azure #2192
- Update 20.2.200: flashgrid-diags iptables numeric output #2166
- Update 20.2.192: Diags showing warning: Python 2 is deprecated #2148
- Update 20.2.187: multiple DB homes in diags and HealthChecker #2050
- Update 20.2.28: after diags update node monitor logs errors about /u01 mount point #2030
- Time warp alert after starting nodes #2010
Version 19.06
New features:
- HTTP proxy for REST alerts and uploads #1868
Bug fixes:
- Build 19.6.213: Node monitor service failing and restarting on systems with busy i/o #1816
- avoid splitting alerts in multiple emails #1872
- after set-email-alerts, node-monitor keeps using old emails for sending alerts #1873
- change CPU load measurement period from 10s to 20s #1886
- change "high disk latency" events to Warning #1885
- remove /etc/ file control from auditd rules #1894
Version 19.05
New features:
- "Call home" alerting mechanism #1824
Bug fixes:
- enhancement of CPU usage dump #1855
- dmesg timestamps in human readable format #1843
Version 19.03
New features:
- added GCP support
Bug fixes:
- Remove extra formatting in node-monitor logs #1801
Version 19.02
New features:
- capture full output of top during low memory and high CPU events #1740
Bug fixes:
- slow reboot after kernel crash because of STAP console output #1720
Version 18.11
New features:
- audit service for tracking and alerting about configuration changes #1698
Bug fixes:
- flashgrid-cluster timing out when ASM not responding #1576
- update 115: high CPU load during system start on quorum nodes #1755
- update 76: Time warp warnings when system is busy #1744
- update 75: process dying during memory consumption check
- update 51: slow reboot after kernel crash because of STAP console output #1720
- update 40: bogus max latencies recorded on NVME EBS disks on AWS #1450
Version 18.10
New features:
- email alerts for events in node monitor logs #1587
- automated upload of diags #1554
- record high CPU utilization #1555
- recored low memory events #1586
- collect diags in parallel for multiple nodes #1588
- collect SAR for 7 days #1585
- add domain name to archive file name #1589
- add user-friendly text to email alerts #1604
- update 68: allow enabling/disabling each type of monitoring #172
Bug fixes:
- update 45: bogus max latencies recorded on NVME EBS disks on AWS #1450
Version 18.04
Initial release
Bug fixes:
- update 114: network monitoring not working with direct iscsi enabled #1531