Set Up Agent for Mac Locally on an Apple Mac

The Agent for End User Devices monitors end user experience by measuring device and application performance. The Agent for Mac monitors the device's details and dynamic resource usage, and its health events, including system and application health events. It also monitors managed and discovered native desktop applications (since version 2.4) and all web applications running in Google Chrome on your Mac:

To monitor a an Apple Mac, run the setup of the Agent for Mac. Start by monitoring a few select Macs to evaluate its features, then you can mass-deploy the Agent to all devices in your enterprise. It sets up as a standard macOS daemon with no visible impact on the user interface.

The setup adds the SteelCentral Agent for Mac for the current user only (user level, not system level), and therefore the Agent is only active when that user is signed in to the computer. It starts automatically when the setup completes or when the user logs in, and stops when the user logs out.

Note

You do not need administrator privileges to set up the Agent for Mac for the current user of the Mac.

The setup package and the extracted Agent files are secure, signed with our certificate. After you set up the Agent, it can communicate securely with the server using the HTTPS protocol on port 443. Learn more about security.

Agent for Mac setup with embedded configuration is secure

You use the same Agent for Mac setup by double-clicking for a single Mac, or by running it from the command line (Terminal window). Use the command line to test your mass-deployment of the Agent for Mac by first running it on a single Mac.

Before you begin

Verify you have Google Chrome on your computer. Agent for Mac requires Google Chrome for the setup to succeed. If not installed, the Agent for Mac setup will fail when trying to install Chrome extensions.

To monitor an Apple Mac with SteelCentral Agent for Mac, it must have the following minimum system requirements:

Attribute Requirement
Agent for Mac

Supported Agent for Mac versions: 2.4, 3.0, 3.1.x

Mac operating system

macOS 10.14 (Mojave) (since version 3.1), macOS 10.13 (High Sierra) (since version 2.4), macOS 10.12 (Sierra), OS X 10.11 (El Capitan), or OS X 10.10 (Yosemite)

Processor

Mac computer with Intel 64-bit CPU.

Resource usage

The Agent for Mac typically uses:

  • CPU: Total utilization across all cores less than 1%.

  • RAM: The SteelCentral Agent for Mac uses approx. 200-300MB of physical memory.

  • Storage: At least 0.5GB free disk space available.
  • Bandwidth: Network traffic load overhead increases by approx. 0.02 kilobytes per second (KBps) incoming to the device, and approx. 0.05KBps reporting data to Aternity.

Monitor web applications

Monitor any web application in any version of Google Chrome released in the past two years. For legacy Agents (on Windows until Agent 9.1.x or on Mac until Agent for Mac 2.3), you must also manually add the Aternity Extension for Chrome to monitor web page load events (WPM) and usage.

Procedure

  1. Step 1 Download the SteelCentral_Aternity_MacAgent_3.1.246.zip file from the Riverbed support site and unpack it.

    The content will be extracted to the same directory in which your zip file resides.

    The zip includes the following files:

    Field Description
    SteelCentral_Aternity_MacAgent_3.1.246_Create_Pkg.sh

    This file creates the Agent for Mac installation package (pkg).

    SteelCentral_Aternity_MacAgent_3.1.246_Agent_Conf.json

    A sample configuration json file that you can use as an input to the script.

    SteelCentral_Aternity_MacAgent_3.1.246_Install-Chrome-Ext

    This file is required for mass deployment of Chrome extension which is necessary for web monitoring.

    SteelCentral_Aternity_MacAgent_3.1.246_Uninstall-Chrome-Ext

    This file uninstalls the Chrome extension.

  2. Step 2 Use the Terminal window to generate the setup pkg file.
    usage: SteelCentral_Aternity_MacAgent_3.1.246_Create_Pkg.sh
                    -configuration CONFIGURATION_FILE | (-aggregation_server AGGREGATION_SERVER [-proxy PROXY])
                    [-output OUTPUT_PATH]
    
    Command arguments:
      -configuration CONFIGURATION_FILE, -c CONFIGURATION_FILE
                            Full path and name to JSON configuration file
      -aggregation_server AGGREGATION_SERVER, -a AGGREGATION_SERVER
                            Aggregation server URL or IP
      -proxy PROXY, -p PROXY
                            Proxy URL and port in the form <proxy url>:<port>
                            Valid only when -aggreagtion_server specified
      -output OUTPUT_PATH, -o OUTPUT_PATH
                            Output directory for the PKG
                            Default is the current directory
    
    Field Description
    CONFIGURATION_FILE

    A sample configuration json file that you can use as an input to the script.

    Either CONFIGURATION_FILE or AGGREGATION_SERVER parameter is mandatory.

    AGGREGATION_SERVER

    Set this parameter to the address of your Aternity Aggregation Server (URL or IP). Use https for secure connections (learn more).

    To add a redundant (set of) Aggregation Servers to switch to another if one fails (failover), enter the redundant server addresses after this one (learn more).

    PROXY

    (Optional) To communicate via a proxy server, add Proxy URL and port in the form <proxy url>:<port>.

    You can use this parameter only in addition to the AGGREGATION_SERVER parameter, but not with CONFIGURATION_FILE.

    OUTPUT_PATH

    Set the output directory for the generated pkg file, if you want to keep the generated pkg file not in the directory from which you run the script.

    For example, in the directory of the pkg file, enter:
    ./SteelCentral_Aternity_MacAgent_3.1.246_Create_Pkg.sh -a https://aternity-epm.my-server.com
    The .pkg file has been created and saved to the same directory in which you executed the script.
  3. Step 3 Set up the customized Agent for Mac by launching the .pkg file.

    The customized Agent setup pkg file has the proper server address. If you use a proxy server in your organization, contact the Aternity Beta Team to add this information to the setup.

  4. Step 4 Select Install for me only and complete the setup.

    You're done!

    Important

    If you try to set up the Agent for Mac for all users, or if it asks for an administrator's username and password, the setup will fail. You can only set up for this user.

    Select to set up for this user only
  5. Step 5 To verify your setup of SteelCentral Agent for Mac:
    1. a Open Applications > Utilities > Activity Monitor and search for the word Aternity.

      Verify it lists AternityAgent as a running process.

      See the SteelCentral Agent for Mac running
    2. b Open a browser and sign in to Aternity.
    3. c Select the device icon in the top bar of any dashboard to view details of your computer.
      Verify the number of monitored devices
  6. Step 6 To monitor web applications in Google Chrome, quit (cmd-Q) and reopen your browser.

    The setup automatically adds the Aternity Extension for Chrome to the local Chrome browser. Confirm you accept this change by selecting Enable Extension.

    Tip

    Setup deploys this automatically from Agent 9.2.x or Agent for Mac 2.4. However, it requires that the device is part of the enterprise's domain, and it can download from the Chrome Web store. If the device does not add it automatically, you can deploy it manually (learn more).

    Confirm monitoring web applications in Google Chrome for Mac