Domotz Collector
10K+
Domotz Network Monitoring and Management
Domotz is a cloud-based network monitoring and management software designed to help you discover, monitor, and manage your network and assets without overspending. Domotz gives you full-context visibility and a suite of management features so you can uncover blind spots to avoid surprises, save time and money with faster and easier issue resolution, and exceed service delivery expectations.
Subscription Requirement
Domotz requires a subscription to its service described at www.domotz.com. View transparent pricing at www.domotz.com/pricing.
Why Domotz?
Networks are increasingly diverse and distributed, making it harder for IT teams to command their network and connected devices. Without proper network monitoring and management, teams are stuck reacting to unexpected issues, dealing with blind spots, slow troubleshooting, and outages that necessitate damage control.
Domotz gives IT teams full-context visibility into every device and connection across their networks, eliminating blind spots and enabling proactive management. With real-time alerts, remote access, network topology, and powerful diagnostics, teams can identify and resolve issues faster, often before they impact users. This means less time fighting fires and more time focused on keeping networks stable and users happy.
Try Domotz for free and take advantage of all our features:
The Domotz Difference
Start the Docker container as a background service:
docker run --network=host --cap-add NET_ADMIN -d domotz/domotz-collector
Then, open the configuration interface in your browser:
http://localhost:3000
To retain your Domotz Collector configuration after container restarts or rebuilds:
Create a persistent config directory on the host:
mkdir -p /absolute_path_to_local_directory/config/
Create an empty configuration file:
touch /absolute_path_to_local_directory/config/domotz.json
Run the container with a volume mapping for the config file:
docker run --network=host --cap-add NET_ADMIN \
-v /absolute_path_to_local_directory/config/domotz.json:/opt/domotz/etc/domotz.json \
-d domotz/domotz-collector
Add the following to your docker-compose.yml file:
services:
domotz-collector:
image: "domotz/domotz-collector"
network_mode: "host"
container_name: domotz-collector
volumes:
- /absolute_path_to_local_directory/config/domotz.json:/opt/domotz/etc/domotz.json
cap_add:
- NET_ADMIN
restart: unless-stopped
By default, the Domotz Collector configuration interface is available at port 3000. If you'd like to run it on a custom port, you can do so by setting the LISTEN_PORT environment variable when starting the container.
For example, to run the Domotz Collector on port 3001:
docker run -e LISTEN_PORT=3001 --network=host --cap-add NET_ADMIN -d domotz/domotz-collector
Then, access the configuration interface at: http://localhost:3001
Note: Custom port configuration works only when the LISTEN_PORT environment variable is set and must be used in conjunction with --network=host on Linux-based systems.
To resume configuration without creating a new Domotz entity (Note: This is not compatible with --network=host):
docker run --mac-address 02:42:AC:12:00:03 ...
On Mac and Windows, the container cannot discover or monitor devices on the host network. However, it can monitor the Docker daemon network and other running containers.
To launch the container and access the configuration interface on port 3000:
docker run --publish 3000:3000 -d domotz/domotz-collector
Content type
Image
Digest
sha256:ab40eeaf5…
Size
289.7 MB
Last updated
11 days ago
docker pull domotz/domotz-collector