Audience: Riva Administrators.
Issue
Exchange server traffic may spike from time to time.
Troubleshooting
Spikes in Exchange server loads must be traceable for troubleshooting purposes. Exchange administrators need to know which traffic is Riva-related.
We recommend giving Riva traffic a specific user agent type. This function allows administrators to determine the origin of mail server traffic. Adding a Riva-specific header to the Exchange connection can help determine if Riva is contributing to heavy Exchange traffic.
Implementation for Riva Cloud
Implementation for Riva On-Premise
Proceed as follows:
To add a Riva-specific header to the Exchange connection:
-
Add the following advanced option to the Exchange connection:
Sync.Ex.SendDebugXRivaHeader = True
Result: An "X-Riva" header is added to all EWS requests. The header includes the current version number of Riva in use.