Docs » Administer Your Organization » Allow Splunk Infrastructure Monitoring and Splunk APM services

Allow Splunk Infrastructure Monitoring and Splunk APM services 🔗

Splunk Infrastructure Monitoring and Splunk APM are composed of a number of different services. For organizations with more stringent networking security policies around sending data to third parties, you can use one of the following mechanisms to ensure access to these services:

If your policies require that you identify static IP addresses, then choose one of the first two options.

Use a simple http/https proxy 🔗

If you can get out to the WWW via proxy, then this is your simplest option. collectd supports communicating over an https proxy, as does the SignalFx Gateway (formerly called the metric proxy).

Use the SignalFx Gateway 🔗

You can run the SignalFx Gateway itself (formerly called the metric proxy) in a DMZ.

Allow URLs through proxy 🔗

Note about realms

A realm is a self-contained deployment of Splunk Infrastructure Monitoring or APM in which your organization is hosted. Different realms have different API endpoints. For example, the endpoint for sending data in the us1 realm is https://ingest.us1.signalfx.com, while the endpoint for sending data in the eu0 realm is https://ingest.eu0.signalfx.com.

Where you see a placeholder that refers to realms, such as <REALM> or <YOUR_REALM>, replace it with the actual name of your realm. You can find this name on your profile page in the user interface. If you don’t include the realm name when specifying an endpoint, Infrastructure Monitoring defaults to the us0 realm.

If your organization’s networking security policies require services delivered over the Internet to be individually allowed, please ensure that the following URLs are allowed through your proxy:

YOUR_SIGNALFX_REALM.signalfx.com

\*.signalfx.com

\*.YOUR_SIGNALFX_REALM.signalfx.com

Allow individual domains 🔗

If you are unable to allow all domains that match *.signalfx.com or *.YOUR_SIGNALFX_REALM.signalfx.com as shown above, you can allow the following:

signalfx.com

api.YOUR_SIGNALFX_REALM.signalfx.com

app.YOUR_SIGNALFX_REALM.signalfx.com

backfill.YOUR_SIGNALFX_REALM.signalfx.com

customer-api.YOUR_SIGNALFX_REALM.signalfx.com

ingest.YOUR_SIGNALFX_REALM.signalfx.com

stream.YOUR_SIGNALFX_REALM.signalfx.com

dl.signalfx.com

www.signalfx.com

info.signalfx.com

blog.signalfx.com

developers.signalfx.com

docs.signalfx.com

support.signalfx.com

community.signalfx.com