Platform
The InfraSonar cloud platform is hosted on the Google Cloud Platform.
Data from a monitored environment is received and processed in the InfraSonar cloud platform on what we call the Hubs. These Hubs evaluate the data against configured conditions and store received time series data in SiriDB. Received state data is kept in memory by the Hubs.
ThingsDB in our main back-end and the conductor of our Hubs which are in essence micro-services.
Connection points
| service | source | destination | TCP Port |
|---|---|---|---|
| Frontend | any | app.infrasonar.com | 443 |
| API | any | api.infrasonar.com | 443 |
| HUB | any | hub.infrasonar.com | 8730 |
| InfraSonar Service | 34.90.55.73 and 34.90.105.247 | any | any |
Notes
Fronted
Users connect to our frontend using their web browser. This connection is SSL encrypted and users are required to logon using their Google or Microsoft identity.
API
The API endpoint is used by our agents and can be used for automation tasks. API request require the use of a token
HUB
Probes send their data to the Agentcore. In most scenarios the Agentcore and probes are deployed using an InfraSonar appliance running in a customer environment.
The Agentcore connects to hub.infrasonar.com using TCP port 8730 or TCP port 443.
Play nice and avoid using TCP port 443
TCP port 443 can be configured as a fallback as most firewalls don't inspect traffic properly. We do advise however to keep friends with your firewall administrator and use TCP port 8730 as we use an encrypted streaming protocol and not HTTPS what would be expected on TCP port 443
InfraSonar Service
InfraSonar services connect to supported platforms using the protocol, URL or FQDN provided by the user or configured in the collector. In some scenario's our IP addresses must be authorized to allow data retrieval.