When Collectors first startup they attempt to make an initial connection to the service in US1. If the customers Organizationsu is within another deployment, US2, Dub, Syd, JP or Germany etc the service will properly redirect the Collector to the Collector service URL for that deployment. This is not typically an issue, unless the customer has implemented firewall rules to allow outbound traffic to only the IP's associated with the deployment they have selected.
When this occurs the Collectors initial check to the US1 deployment will fail and the Collector will be unable to start.
To get passed this issue we need to tell the Collector which service URL to use for connecting to the selected deployment so it bypasses the initial request to US1. This can be done within user.properties file by adding the following parameter.
url= <deployment URL>
The deployment URLs for the current deployments are:
Deployment | URL |
US2 | https://collectors.us2.sumologic.com |
Dublin | https://collectors.eu.sumologic.com |
Sydney | https://collectors.au.sumologic.com |
Japan | https://collectors.jp.sumologic.com |
Germany | https://collectors.de.sumologic.com |
Canada | https://collectors.ca.sumologic.com |
FE |
https://collectors.fed.sumologic.com
|
For more info and complete list of deployment URL see : Sumo Logic Endpoints and URL
Comments
0 comments
Please sign in to leave a comment.