AppDynamics switched from Semantic Versioning to Calendar Versioning starting in February 2020 for some agents and March 2020 for the entire product suite.


    Skip to end of metadata
    Go to start of metadata

    You are viewing an old version of this page. View the current version.

    Compare with Current View Page History

    « Previous Version 3 Next »

    On this page:

    Related pages:

    Your Rating:
    Results:
    1 Star2 Star3 Star4 Star5 Star
    1 rates
    Synthetic jobs are configurable, scheduled tests consisting of URL measurements or synthetic scripts. To create a job, see Get Started with Browser Synthetic Monitoring.  

    Synthetic Job Locations

    For URL measurements and synthetic script jobs, the Synthetic Agent is always run in the configured browser location. The synthetic script, however, is not run on the same machine or location as the configured browser for security reasons. See Synthetic Agent Locations for more details.

    Synthetic Job Queue

    When you create a job, it is added to a queue based on the creation timestamp. Scheduled jobs are assigned a maturity level that influences when they will be executed in the queue. On-demand jobs are placed in the same queue but are not assigned a maturity level. 

    Maturity Level for Scheduled Jobs

    Jobs are assigned a maturity level based on when they are created and added to the queue. The following table describes the two supported maturity levels.

    Maturity LevelDescription
    JuniorThis maturity level consists of the synthetic jobs that were just created or updated within the last two hours. Once two hours have passed since the last update or creation of the job, the job will be promoted to Senior. The promotion from Junior to Senior is only performed when the required capacity has been allocated to avoid negatively affecting the currently executing jobs.
    SeniorThis maturity level consists of scheduled jobs that have been created or updated more than two hours ago. The synthetic jobs with the maturity level of Senior have been allocated resources to be executed.

    Synthetic Job Execution 

    The execution order of synthetic jobs depends on the job priority and the job creation time. The Synthetic Server job marks the priority of a job based on several factors: the job type, job maturity, and your Browser Synthetic Monitoring license. 

    Job Execution Order

    The following table shows the job priority based on the job type, license type, and job seniority. The actual job execution order depends on the job priority and job creation timestamp. 

    Job PriorityJob TypeLicense TypeJob Seniority
    HighScheduledProSenior
    ScheduledTrialSenior
    On-DemandProN/A
    On-DemandTrialN/A
    On-DemandLiteN/A
    LowScheduledTrialJunior
    ScheduledProJunior

     

    Synthetic Job Throttling

    Synthetic jobs are only executed if they are in the job queue. If the max job queue size has been reached, however, no additional synthetic jobs will be added to the queue until the queue size decreases. The max queue size is defined by the priority, license, type, and maturity level.

    The following table shows how the maximum queue size is calculated:

    Max Queue SizeJob PriorityJob TypeJob Maturity
    Number of Synthetic Agents * 10 (Pro)High ScheduledSenior
    Number of Synthetic Agents * 10 * 0.5 (Trial)
    Number of Synthetic Agents * 10 * 0.25On-DemandN/A
    Number of Synthetic Agents * 10 * 0.5LowScheduledJunior

     

    Job Execution Errors

    Customer is seeing different error messages with synthetic jobs and will like to understand their meaning and get more information to help with checking the issue at their end. 

    Error MessageCause of ErrorError Code
    Skipped; still waiting for a previous job executionAn attempt was made to queue a high-priority measurement request from a scheduled job before the previous measurement request from the same job and location-browser combination has been processed.TARDY
    Skipped while new capacity is being addedAn attempt was made to queue a low-priority measurement request from a scheduled job before the previous measurement request from the same job and location-browser combination has been processed.TARDY_ONBOARDING
    Skipped while new capacity is being addedAn attempt was made to queue a measurement request from a junior job beyond the maximum respective queue capacity.ONBOARDING
    Testing location is overloadedAn attempt was made to queue a measurement request from a senior job beyond the maximum respective queue capacity.THROTTLED
    • No labels