Agents Administration - Tests
 

Configuration of PureHGrpCapTest

Using this test, administrators can monitor each host group connected to the FlashArray and can pin point the host group that is utilizing the maximum space than the rest. This way, irregularities in the space utilization across the host groups can be detected at ease!. In addition, the test also proactively alerts administrators to probable slowdowns in I/O processing by specific host group, thereby enabling administrators to initiate pre-emptive actions.

The default parameters associated with this test are as follows:

  • The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

  • In the HOST text box, the host for which the test is to be configured has to be specified.

  • In the PORT text box, specify the port at which the specified host listens to. By default, this is set to 9736.

  • The eG agent collects the required metrics from the Pure Storage FlashArray by executing API commands using Pure Storage REST API on the FlashArray and pulls out critical metrics. In order to collect metrics, the eG agent should be provided with a valid API token. To know how to determine the API token, do the following:

    • Login to the Purity GUI as a user with administrator privileges.

    • Then, navigate to the System tab and click on the Users -> API Tokens. The API Tokens page will be displayed in the context-sensitive right panel. The API Tokens page displays a list of all users with API tokens and the dates on which the API tokens were created.

    • To view the API token of the created user, right click on that user. A drop-down list will appear next. Clicking the Show API Token option in that list reveals the API Token generated for the created user in a separate pop up window.

    • Copy this API token and specify the same in the API TOKEN text box while configuring the tests.

    Specify the determined API token in the API TOKEN text box.

  • The DD FREQUENCY refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 2:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD FREQUENCY.

  • To make diagnosis more efficient and accurate, eG embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test, by default, for a particular server, choose the Onoption against DETAILED DIAGNOSIS. To disable the capability, click on the Off option.

    The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

    • The eG manager license should allow the detailed diagnosis capability.

    • Both the bad and normal frequencies configured for the detailed diagnosis measures should not be 0.

  • If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

  • Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.