Brief maintenance outage Tuesday, August 20

This site, docs.bmc.com, will undergo a brief maintenance outage on Tuesday, August 20 at 6 pm CDT. Downtime will be less than five minutes.

    Page tree
    Skip to end of metadata
    Go to start of metadata

    You can edit the App Visibility collector.properties file to change the way Synthetic Monitor Execution errors and Accuracy errors are classified. It is important to make the change on all of your App Visibility collectors simultaneously to maintain consistency. The file is located in the following directory of the collector installation:

    • Windows
      installationDirectory\collector\properties
    • Linux
      installationDirectory/collector/properties

    Note

    After you change the collector.properties file, restart the collector service.

    To change the classification of Synthetic Execution errors

    1. Open the collector.properties file.
    2. Search for the synthetic.execution.to.availability.error.mapping field.

      synthetic.execution.to.availability.error.mapping=none
    3. Modify the value as follows:
      • none - (default) No Execution errors are classified as Availability errors.
      • timeout - Timeout Execution errors are classified as Availability errors.
      • all -  All Execution errors are classified as Availability errors.
    4. Restart the App Visibility collector service.

    The change takes effect immediately for all errors detected after the change. The change does not have any effect on historic data. 

    Note

    In the Synthetic Health tab, names of transactions with severe Execution errors may appear as N/A . This is also true for Execution errors that are reclassified as Availability errors.


    To change the classification of Synthetic Accuracy errors

    1. Open the collector.properties file.
    2. Search for the synthetic.accuracy.to.availability.error.mapping field.

      synthetic.accuracy.to.availability.error.mapping=false
    3. Change the value as follows:
      • false - (default) Accuracy errors are not classified as Availability errors.
      • true - Accuracy errors are classified as Availability errors.
    4. Restart the App Visibility collector service.

    The change takes effect immediately for all errors detected after the change. The change does not have any effect on historic data. 

    Related topics

    Changing App Visibility collector settings

    Changing App Visibility portal settings

    Starting and stopping the App Visibility server services

     

    2 Comments

    1.  

      1.