App Visibility - App Visibility events are not closed when they are manually closed in the Truesight Infrastructure Management (TSIM) console

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:

    TrueSight App Visibility Manager Server


    COMPONENT:

    App Visibility Portal


    APPLIES TO:

    App Visibility Portal - all versions



    QUESTION:

    When manually closing an App Visibility event in the Truesight Infrastructure Management (TSIM) console, the same App Visibility event is not closed in the TrueSight Presentation Server (TSPS) console nor in the App Visibility Portal console.

    How does one close an App Visibility event from the TSIM console?


    ANSWER:

     

    If the App Visibility event (Synthetic, App Visibility Agent for Java, or App Visibility Agent for .NET event) is manually closed in the Events page from within the TSIM console then it will close the event in TSIM. However, that same App Visibility event will not be closed in the TSPS console nor the App Visibility Portal console.  The reason is because the Events page in the TSIM console is controlled by TSIM and it does not reflect back to the App Visibility Portal.

    Note:
    There is not an option to sync the App Visibility events if they were manually closed in the TSIM console.

    To properly close a Synthetic event, perform the following:
    The user would need to go into the Synthetic Health tab of the Synthetic application from the TSPS console and close the event. If the user close the Synthetic event anywhere else within the TSPS console, it will not close the event in the App Visibility Portal.

    To summarize the improper and proper ways of closing an App Visibility event in TrueSight, see below:

    1) If the user manually closes the event in the TSIM console (Events page) then it will close the event in TSIM, but it will not close that same event in the App Visibility Portal. The Events page in the TSIM console is controlled by TSIM and it does not reflect back to the App Visibility Portal.

    If this action was performed, then go into the Synthetic Health tab of that Synthetic application in the TSPS console and manually close the event.

    2) If the user manually closes the event in the Events page within TSPS console then the Synthetic event will not close properly in the App Visibility Portal. It will not sync across the board.

    If this action was performed, then go into the Synthetic Health tab of that Synthetic application in the TSPS console and manually close the event.

    3) If the user manually closes the event in the Synthetic Health tab within the Synthetic application on the TSPS console (Monitoring -> Application web page) then the event will be close in the App Visibility Portal, and it will be reflected in the App Visibility Portal and TSIM console properly.

    4) Wait until the application changes back to an OK state

    To properly close an App Visibility Agent for Java or App Visibility Agent for .NET event, perform the following:
    The user can stop the App Visibility Agent for Java or App Visibility Agent for .NET agent for ~10 minutes.  The events will be closed, which can be verified by ensuring the Tier colors are in green within the Application view in the TSPS console.  Then restart App Visibility Agent for Java or App Visibility Agent for .NET agent.  Once the App Visibility Agent for Java or App Visibility Agent for .NET agent is up and running, if there are still ‘bad’ transactions then a new event will be created.

     


    Article Number:

    000161905


    Article Type:

    FAQ/Procedural



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