The gadget spec URL could not be found
The following parameters are used to configure the data collection agents for Greenplum Command Center The gadget spec URL could not be found
gp_enable_gpperfmon and gpperfmon_port must be set in both the master and segment postgresql.conf files. gp_enable_gpperfmon and gp_enable_gpperfmon only need to be set in the master postgresql.conf file. After changing these settings, the Greenplum Database instance must be restarted for the changes to take effect. gp_enable_gpperfmon Turns on the Command Center data collection agent for a segment. Must be set in all postgresql.conf files (master and all segments). [gpadmin@sachi scripts]$ gpconfig -s gp_enable_gpperfmon Values on all segments are consistent GUC : gp_enable_gpperfmon Master value: on Segment value: on The gadget spec URL could not be found gpperfmon_port The default port for the Command Center agents is 8888, but you can set this parameter to a different port if required (master and all segments). [gpadmin@sachi scripts]$ gpconfig -s gpperfmon_port Values on all segments are consistent GUC : gpperfmon_port Master value: 8888 Segment value: 8888 [gpadmin@sachi scripts]$ gp_gpperfmon_send_interval Sets the frequency in seconds that the Greenplum Database server processes send query execution updates to the Command Center agent processes. [gpadmin@sachi scripts]$ gpconfig -s gp_gpperfmon_send_interval Values on all segments are consistent GUC : gp_gpperfmon_send_interval Master value: 1 Segment value: 1 [gpadmin@sachi scripts]$ gp_external_enable_exec This parameter is enabled by default and must remain enabled. It allows the use of external tables that execute OS commands or scripts on the segment hosts. The Command Center agents use this type of external tables to collect current system metrics from the segments. [gpadmin@sachi scripts]$ gpconfig -s gp_external_enable_exec Values on all segments are consistent GUC : gp_external_enable_exec Master value: on Segment value: on The gadget spec URL could not be found | The gadget spec URL could not be found The gadget spec URL could not be found |
