eG Administration
 

Configuring Virtual Center Events

This test enables administrators to promptly capture and report the count and details of critical information, error, warning, and user events that are generated on the vCenter server. By default, the test monitors a pre-defined set of events belonging to pre-configured event categories. You can override this default setting by including/excluding specific events from an event category. To achieve this, do the following:

  • Login to the eG administrative interface.
  • To access this page, click on the icon available in the Admin tab. Then, select the Settings option in the Agents tile.
  • Click on the VCenter Events option from the Agent Settings tree. Alternatively, you can also click on the Click here hyperlink that is available above the parameters of this test in the Test configuration page. Either way, VCENTER EVENTS page appears.
  • Select an Event category to be monitored.

Note:

By default, the Event category list in VCENTER EVENTS page displays a pre-configured set of event categories. You can make more event categories available for selection in this list or remove one/more of the pre-defined categories, if need be. To achieve this, follow the steps given below:

  • Edit the eg_tests.ini file in the <EG_INSTALL_DIR>\manager\config directory.
  • In the [VirtualCenterEvents] section of this file, you will find the default event categories that will populate the Event category list of VCENTER EVENTS page and the individual events of each category. The format of these default entries is:

    VCEventsTest:<EventCategory>=<Comma-separated list of events belonging to this category>

    • VCTaskEvtTest:<EventCategory>=<Comma-separated list of events belonging to this category>

  • To add a new event category to this default list, you just need to append a line to the [VirtualCenterEvents] section in the format mentioned above. For instance, say, you want to include a category named NfcService to the Event category list of VCENTER EVENTS page. In this case, you will have to insert a line in the [VirtualCenterEvents] section for this category, as mentioned below:

    • VCEventsTest:NfcService=NfcService.randomAccessOpen,NfcService.randomAccessOpenReadonly,NfcService.getVmFiles,NfcService.putVmFiles, NfcService.fileManagement,NfcService.systemManagement

  • Next, proceed to the [VCEventFilterTypes] section of the eg_tests.ini file. For every event category that is defined in the [VirtualCenterEvents] section, a corresponding entry should exist in the [VCEventFilterTypes] section. If not - i.e., if an event category exists only in the [VirtualCenterEvents] section and not in the [VCEventFilterTypes] section-then, such an event category will not be listed as an option in the ‘Event Category’ list box of VCENTER EVENTS page.
  • Typically, the [VCEventFilterTypes] section is used to indicate which events of a particular category need to be monitored by default, and which are not to be monitored. The entries to this section need to be of the following format:

    • VCEventsTest:<EventCategory>=<Comma-separated list of events to be included while monitoring>:<Comma-separated list of events to be excluded from monitoring>

    To include/exclude all events of a particular category, use the keyword all, and to ensure that no events of a certain category is included/excluded, use the keyword none.

  • For instance, to ensure that all the events of the Alarms event category, except the alarm.Alarm.setCustomValue event, is to be monitored by default, your specification would be:

    VCEventsTest:Alarms=all:alarm.Alarm.setCustomValue

  • Once entries for the new event category are inserted in both the sections, save the eg_tests.ini file.
  • Selecting an Event category displays the tasks of the chosen category that are by default included for monitoring in the INCLUDED EVENTS list, and those that are by default excluded from monitoring in the EXCLUDED EVENTS list.

    • Note:

  • Every event category that is defined in the [VirtualCenterEvents] section of the eg_tests.ini file (in the <EG_INSTALL_DIR>\manager\config directory) is associated with a set of events. Typically, to indicate which of these events need to be monitored by default, and which are not to be monitored, the [VCEventFilterTypes] section of the eg_tests.ini file is used.
  • For every event category defined in the [VirtualCenterEvents] section, a corresponding entry should exist in the [VCEventFilterTypes] section indicating the default set of events to be included and/or excluded from monitoring. This entry should be of the following format:

    • VCEventsTest:<EventCategory>=<Comma-separated list of events to be included while monitoring>:<Comma-separated list of events to be excluded from monitoring>

  • To include/exclude all events of a particular category, use the keyword all, and to ensure that no events of a certain category is included/excluded, use the keyword none.
  • For instance, to ensure that all the events of the Alarms event category, except the alarm.Alarm.setCustomValue event, is to be monitored by default, your specification would be: VCEventsTest:Alarms=all:alarm.Alarm.setCustomValue
  • This makes sure that if the Alarms option is chosen from the Event category list of VCENTER EVENTS page, the EXCLUDED EVENTS list by default displays the event, alarm.Alarm.setCustomValue, and the INCLUDED EVENTS list displays all other events associated with the Alarms category.

    • Note:

  • While using the [VCEventFilterTypes] section to configure specific events to be included/excluded by default for an event category, make sure that such events are a sub-set of the events that have been defined for that category in the [VirtualCenterEvents] section. For instance, say, you do not want to monitor the alarm.Alarm.setCustomValue event of the Alarms category. To ensure this, you will have to include the following line in the [VCEventFilterTypes] section:

    • VCEventsTest:Alarms=all:alarm.Alarm.setCustomValue

  • However, before adding this line to the [VCEventFilterTypes] section, verify whether the event, alarm.Alarm.setCustomValue is available in the list of events that have been defined for the Alarms category in the [VirtualCenterEvents] section.
  • Make sure that entries such as the following are not inserted in the [VCEventFilterTypes] section:

    • VCEventsTest:<EventCategory>=all:all

    VCEventsTest:<EventCategory>=none:none

  • Also, note that the keywords all and/or none should not be part of a comma-separated list.
  • To include any of the events that are by default listed in the EXCLUDED EVENTS list, select the event from the list and click the < button. Similarly, to exclude any of the events that are by default available in the INCLUDED EVENTS list, select one/more events from the list and click the > button.
  • Finally, save the changes by clicking on the Update button.