What are the Best Practices for reducing CPU consumption using continuous monitoring with MainView Explorer?

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    MainView Explorer


    APPLIES TO:

    MainView Explorer



    QUESTION:

    MainView Infrastructure: All Versions
    MainView Explorer: All Versions

    What are the Best Practices for reducing CPU consumption using continuous monitoring with MainView Explorer?


    ANSWER:

     

    Legacy ID:KA409870

      

    Recommendations for reducing CPU consumption using continuous monitoring with MainView Explorer

      

    Many CPU usage issues are related to users using MainView Explorer with Auto-Refresh at short intervals or not filtering with WHERE/QWHERE. The following recommendations are suggested to help reduce the CPU consumption using continuous monitoring with MainView Explorer.

      

    1) Use the highest Auto-Refresh rate that provides appropriate monitoring. A refresh rate of 2 minutes is much less costly than 15 or 30 seconds. Auto-Refresh can be set at the view or container level.

      

    2) Use alarms and alerts to notify users of exceptional conditions.

      

    3) Avoid continuous monitoring of views with many thousands of rows. Add QWHERE to limit the amount of data returned before filtering and thresholds are applied.

      

    4) Use "Open Alternate Chart" to display different charts for the same view data. This utilizes the query that was established in the base view and chart. Opening a new chart or view, or opening a chart with no backing view ("Open Chart" function from the product tree) starts a new query.

      

    5) Use FORM commands to display view data in different formats. This utilizes the query that was established in the base view. A customized form (view) can include or exclude columns, add filters and a WHERE clause, and set different thresholds to display the data as desired.

      

    6) Use 'Export view data' to publish view data to a shared location on the network. The views can then be opened by users of the MVE Viewer, which does not require access to the host server and consumes no additional host resources.

      

    7) Use 'Export view image' and 'Export container image' to publish images to a shared location on the network. These images can be loaded into a browser on any device with access to the enterprise network.

      

    8) Build configurations of views, containers, and charts and export them. Other users of the MVE Client or MVE Viewer can open the configurations.

      

    Refer to Help...What's New for information about publishing view data, configurations, and containers. Typically a dedicated server or workstation publishes data for MVE Viewer and browser access.

      

    MainView Explorer will create history files of view contents that are stored on the PC or a network drive. Even views that do not support Interval data (such as CTRAN) can use this short-term history feature. On the "Refresh" tab of the Properties dialogue is an option "Preserve history with each refresh". A dropdown allows the user to choose from a list of possible numbers of files to keep. Turn on 'Export view data' to create the history files and use the blue arrows to navigate through them. Each file is a copy of the view data captured at each refresh. MVE Viewer users can also navigate the history since it is exported to the same network location as the regular view data.

      

    Refer to Using Short-term History with Export under Help...What's New for more information.

      
    Related Products:  
       
    1. MainView Infrastructure

     


    Article Number:

    000029925


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles