Skip to main content
To be able to send notifications or error information you need to make sure your network is configured for this. This can be done either directly to the service or through an HTTP proxy.

​
HTTP proxy

Validio supports using HTTP proxy for outbound communication for Slack, MS Teams and Sentry. The URLs for both http_proxy and https_proxy can be the same, it’s internally in the application that they are used for http respectively https URLs.

​
Self-signed certificate for HTTP proxy

If you need to add a self signed CA certificate to the trust store for HTTP proxy, you can do that using helm values. The content can be one or more CA certificates in PEM format. Here is an example:
YAML

​
Slack

Use the following configuration to enable HTTP proxy for Slack
YAML
The following destinations will be used by Validio to send notifications to Slack, so make sure they are whitelisted in your network or in your HTTP proxy
Text
The wss-*.slack.com hosts are only needed when interactive messages are enabled. They power the Socket Mode WebSocket connection and are assigned dynamically by Slack at connection time (via slack.com/api/apps.connections.open), so allowlist all three. For the full endpoint and path-based allowlisting breakdown, see the Slack integration documentation.

​
MS Teams

Use the following configuration to enable HTTP proxy for MS Teams
YAML
The following destinations will be used by Validio to send notifications to MS Teams, so make sure they are whitelisted in your network or in your HTTP proxy
Text
The login.botframework.com host is only needed when interactive messages are enabled. Interactive messages also require Microsoft Teams to reach your Validio installation on the /ms-teams-webhook endpoint. For what each endpoint is used for, see the Microsoft Teams integration documentation.

​
Sentry

Use the following configuration to enable HTTP proxy for Sentry
YAML
Make sure the following destinations are whitelisted in your network or HTTP proxy
Text

​
Posthog

Use the following configuration to enable HTTP proxy for Posthog:
YAML
Make sure the following destinations are whitelisted in your network or HTTP proxy:
Text