Using Application Keys

Each repository has a collection of Application Keys that can be managed in the Settings module.  Each application key has a few configuration options:

• Caption & Description: To help tracking what that key should be used for.
• Data Collection Option: Indicate if session data associated with the key should be accepted, blocked, disabled, or suppressed.
• Application Environment Routing: Optional.  The Application Environment that the session data is for.

Application Keys are required for using Loupe Monitor (it determines the Application Environment Routing) and are recommended for general sessions to provide more server control over data collection options.

To use an Application Key to send data to a Loupe Server, specify it in the Server configuration section by using the ApplicationKey setting instead of using the CustomerName or Repository setting.

Creating & Managing Application Keys

There are two places to create or modify Application Keys:

1. Configuring Application Environments: As part of setting up Loupe Monitor, when an Application Environment is being configured Application Keys can added, deleted, and modified. 
2. Repository Settings: In the Settings module of each Loupe Repository the entire list of Application Keys can be administered including creating or deleting repository-wide keys.