Network Requirements

factry historian default ports the following is an overview of the most important components of factry historian and their default listening ports all ports can be changed as needed collectors no listening ports web server as reverse proxy (optional, recommended) listening for tcp traffic on ports 80 (http), 443 (https), 8080 (http(s)) historian server listening for tcp traffic on port 8000, http traffic is usually forwarded by proxy to this port to provide https listening for tcp traffic on port 8001, grpc should be reachable by collectors influxdb time series database listening for tcp traffic on port 8086, http should be reachable by historian server and dashboarding interface should external access be required, https forwarding can be added via the proxy postgresql relational database listening for tcp traffic on port 5432 should be reachable by backend and optionally the dashboarding interface grafana listening for tcp traffic on port 3000, http traffic is usually forwarded by proxy to this port to provide https connectivity general ability to perform dns lookups either through public dns servers or dns servers supplied by the clien t (optional) ability to perform time synchronization with ntp either through public ntp servers or ntp servers supplied by the client (optional, preferred) for monitoring and alerting outgoing tcp traffic to port 443 on host portal factry cloud (for general system monitoring) for remote management/assistance access will be arranged in agreement with the client required access in such cases ssh (with administrative privileges) to the following components backend administration interface time series database dashboarding interface web server access to machines running factry collectors to be decided together with the client for software updates outgoing tcp traffic to ports 80 and 443 to reach official linux package repositories (e g archive ubuntu com, security ubuntu com) and factry’s update portal portal factry cloud clients can choose whether updates are performed by factry remotely (under strict access controls) or by their own it staff following factry’s update instructions this list can be expanded depending on the implementation specifics