The configimport command imports a monitoring policy. The source of the import is an XML file that has been previously exported with the configexport command. A monitoring policy describes all customizations to rules, derived metrics, registry variables, agent settings and persistence policies and is useful in technical analysis and modification tasks.
Specifies the user name and password for the Foglight Management Server, as well as the machine name and port number, if necessary. Alternatively, fglcmd can retrieve this information from a user-specific properties file. For more information on how to specify connection options on the command line, see Logging In and Setting the Scope . For details on using a properties file, see Using a Properties File to Supply Connection Information . | ||
Specifies the path and file name of the XML file that is to be imported. |
The uiexport command exports a UI module to a ZIP file. Use this command to export any modifications to Foglight operational elements such as views, dashboards, and other resources. Given a valid module name and a file path and name, the uiexport command exports the contents of that module into a ZIP file. If required, you can use the output file to re-import that module into the same or a different Foglight server at a later time using the uiimport command.
Specifies the user name and password for the Foglight Management Server, as well as the machine name and port number, if necessary. Alternatively, fglcmd can retrieve this information from a user-specific properties file. For more information on how to specify connection options on the command line, see Logging In and Setting the Scope . For details on using a properties file, see Using a Properties File to Supply Connection Information . | ||
Specifies the path and name of the ZIP file that the UI module is to be exported to. | ||
The following example shows you how to export a module to a ZIP file using the module name as an argument. To get a list of module names, use the uilist command, as shown in Example .
• |
• |
The uiexport command exports a UI module to a ZIP file. Use this command to export any modifications to Foglight operational elements such as views, dashboards, and other resources. Given a valid module name and a file path and name, the uiexport command exports the contents of that module into a ZIP file. If required, you can use the output file to re-import that module into the same or a different Foglight server at a later time using the uiimport command.
Specifies the user name and password for the Foglight Management Server, as well as the machine name and port number, if necessary. Alternatively, fglcmd can retrieve this information from a user-specific properties file. For more information on how to specify connection options on the command line, see Logging In and Setting the Scope . For details on using a properties file, see Using a Properties File to Supply Connection Information . | ||
Specifies the path and name of the ZIP file that the UI module is to be exported to. | ||
The following example shows you how to export a module to a ZIP file using the module name as an argument. To get a list of module names, use the uilist command, as shown in Example .
• |
• |
The uiimport command imports a UI module from a ZIP file. It uses the ZIP file that has been previously imported with the uiexport command as the source of import. A UI module is a collection of Foglight operational elements such as views, dashboards, and other resources.
Specifies the user name and password for the Foglight Management Server, as well as the machine name and port number, if necessary. Alternatively, fglcmd can retrieve this information from a user-specific properties file. For more information on how to specify connection options on the command line, see Logging In and Setting the Scope . For details on using a properties file, see Using a Properties File to Supply Connection Information . | ||
Specifies the path and name of the ZIP file containing the UI module that is to be imported. |
• |
• |
© ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center