Greenplum and GPCC: Missing CSV alert logs after upgrade to version 6.x
Article ID: 418877
Updated On:
Products
Issue/Introduction
After upgrading Tanzu Greenplum Database and Greenplum Command Center (GPCC) to version 6.x, administrators notice that CSV alert log files are no longer generated under the expected gpperfmon directories.
Environment
- Tanzu Greenplum Command Center (GPCC) version 6.x and newer
- Tanzu Greenplum Database version 6 and newer
Cause
Beginning with Greenplum Database 6, the system no longer supports configuring SNMP alerts or sending email notifications directly from the database. The alerting framework was redesigned to integrate natively with GPCC.
GPCC 6.x introduces its own agents that collect metrics and alert data without relying on the legacy gpperfmon processes (gpmmon, gpsmon). All alert and performance information is stored internally within GPCC or in database tables (for example, gpcc_alert_log) instead of generating CSV files.
This change was introduced as part of an architectural modernization to improve performance, reduce redundancy, and centralize alert management.
Resolution
In GPCC version 6.x and newer:
- The legacy gpperfmon agents (gpmmon, gpsmon) are no longer used or required.
- GPCC uses native monitoring agents and a restructured data model for metrics and alerts.
- CSV-format alert logs (gpdb-alert-*.csv) are not produced in fresh 6.x installations.
- Alert events are stored internally in GPCC tables (such as gpcc_alert_log within the gpmetrics schema).
- All alert information is accessible through:
- The GPCC web interface (Alerts view)
- SQL queries against internal GPCC tables
- For in-place upgrades, previously generated CSV alert files may still exist, but new logs will no longer be written in CSV format.
- To review or export alert data, use the GPCC UI or query internal metrics tables. Historical data from earlier versions can be retained for reference, but future alert monitoring should rely on the GPCC 6.x framework.
Additional Information
Feedback
