TS-Synthetic - No Synthetic data in the Synthetic Health or Application tabs or events are not calculating based on mistimed data

Version 1
    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 Synthetic Transaction Monitor with Micro Focus Silk Performer


    COMPONENT:

    BMC Synthetic Transaction Execution Adapter


    APPLIES TO:

    TEA Agents - All Versions App Visibility Manager Portal - All Versions App Visibility Manager Collector - All Versions



    PROBLEM:

    No Synthetic Execution Plan data in the Synthetic Health tab or events are not calculating based on mistimed data

    Seeing the following messages in the Collector logs:
    Jun-08-2017 18:54:20 CST [synthetic] [***] [WARN] - Results are arriving late from AgentID 6
    Jun-08-2017 18:54:29 CST [synthetic] [***] [WARN] - Results are arriving late from AgentID 9
    Jun-08-2017 18:54:44 CST [synthetic] [***] [WARN] - Results are arriving late from AgentID 6
    Jun-08-2017 18:54:51 CST [synthetic] [***] [WARN] - Results are arriving late from AgentID 9
    Jun-08-2017 18:55:34 CST [synthetic] [***] [WARN] - Results are arriving late from AgentID 6
    Jun-08-2017 18:55:34 CST [synthetic] [***] [WARN] - Results are arriving late from AgentID 9 


    CAUSE:

    Not all machines were synced with the NTP server.


    SOLUTION:

    Results are arriving late - Indicates that results are not arriving on time to the App Visibility Manager(AVM) Collector from the Transaction Execution Agent (TEA Agent) .  

    When results are late, data will not be aggregated by the AVM Portal and this results in the empty views in TrueSight Presentation Server or possible events that are not accurate 
     
    To resolve this problem, ensure that all servers with AVM components (AVM Portal, AVM Collector, TEA Agent)  are synced with an NTP server.

    Please be aware that if the systems are synced with AD Sync, then AD Sync allows for a 5 minute difference between systems:
    https://social.technet.microsoft.com/wiki/contents/articles/50924.active-directory-time-synchronization.aspx

    TS-Synthetic evaluates the data every minute to fill in the graphs and create events.  If the timestamp on the data is more than 1 minute different than what is on the AVM Collector system, then this will cause problems with the data and possible false events.

    BMC does not care what is used to sync the systems for time, but the time difference between the systems must be less than 1 minute.


    Article Number:

    000137858


    Article Type:

    Solutions to a Product Problem



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