mPulse Administration: Beacon Settings

Document created by DPM Admin on Jul 14, 2017Last modified by Sheril Joseph on Aug 10, 2017
Version 2Show Document
  • View in full screen mode

Beacon Settings

The following beacon settings are available to Domain Administrators via the Configure Domain box, Beacons tab.

 

Include Synthetic Monitoring Beacons and Bot Beacons

See Synthetic beacons.

Collect Third-Party Analytics

See Data Collection from Third-Party Analytics.

Collect JavaScript Errors

See JavaScript Error Tracking.

Suspend Beacons

Check the Suspend Beacons box if you'd like to stop beacon collection for this domain. If suspend is true then Config.js is no longer returned; nothing is sent back with a 204: No Content response and the Boomerang receives this and stops producing beacons.

 

Strip Query Parameters from Raw Beacon Logs

The Strip Query Parameters from Raw Beacon Logs field, when checked, will strip the query string parameters from the underlying XML (e.g. from the raw beacon logs). Boomerang will normally include the entire request URL and referrer URL in the given beacon. Users who do not want private query data in the URL can check this box to disable beaconing sensitive information.This setting is generally used to preserve the privacy of users whose clients send beacon data.

This feature is also useful to help determine the accuracy of load time measurements in some extreme cases.

 

Strip IP Addresses from Raw Beacon Logs

The Strip IP Addresses from Raw Beacon Logs field, when checked, will strip the Internet Protocol addresses from the underlying XML (e.g. from the raw beacon logs). This setting is generally used to preserve the privacy of users whose clients send beacon data.

Amazon S3 Upload Setup for Domain-Specific Beacon Logs

The Upload raw beacons to S3 field enables the Admin to specify an Amazon Simple Storage Service (S3) account towhich Beacon logs are uploaded. Logs are also uploaded to a default (internal only) SOASTA account.

Note: The following instructions require that the user has Domain Admin rights on the mPulse instances as well as an Amazon S3 account to specify. Refer to mPulse Setup for more about the Configure Domains box.


Doing the S3 Upload Setup

  1.  Select Central > Domains and either open an existing domain or click New to create a new domain. in either case, the Configure Domains box appears. In the shot below, an existing domain has been configured but does not yet have S3 upload enabled.
  1. Check the Upload raw beacons to S3 box to enable the section.
  1. Provide the necessary values for the S3 section fields:
      • S3 Bucket Name – The user-created unique name. This must exist on Amazon before its use here; in essence it is like a folder name. Refer to Amazon S3 Functionality for more information.

    For example, beacon-upload.

      • S3 Region – Specify the S3 Region to use from those that appear in the dropdown. A bucket can be stored in one of several Regions so ensure to select the Amazon Server location where the S3 Bucket Name was created.

    For example, US Standard.

    • AWS Access Key – Enter the account access key to use.
    • AWS Secret Key – Enter the account secret key to use.
  2. Click OK to complete setup.

Once the upload credentials are establish, open the Amazon S3 bucket, which is accessed through your Amazon AWS portal, but which can also be accessed using the Amazon API. Refer to Working with Amazon S3 Buckets for additional information. See also the Amazon S3 FAQ.

Attachments

    Outcomes