HCL Domino Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
There are several existing options for monitoring Traveler. Both of these were used with the Traveler service when it was running in the IBM Connections Cloud:
1) Monitoring Domino/Traveler statistics by a 3rd party service. Domino supports the exporting of statistics to a third party service: https://help.hcltechsw.com/domino/12.0.0/admin/stats_publish_ext.html . Traveler stats are documented here: https://help.hcltechsw.com/traveler/12.0.0/statistics.html. Typically 3rd party services allow you to set monitoring rules when certain statistics meet some threshold (and alert via email, text). For example, a key stat that we used in the cloud was number of threads waiting on a db connection over a 5 minute period. In an HA environment, a backup on getting a db connection indicates an environment issue that will cause all syncs to start failing.
2) Use the endpoint <Traveler endpoint>?action=getStatus
The getstatus request returns a "traveler available" or "traveler not available". It does sufficient checking of Traveler's features for the authenticated user to determine if the server is functioning or not. Its useful to determine a server down scenario when Domino itself may be functioning.