However we now have a new service, hathor-p2p-monitor, that exposes an API that could be used to get the network information needed by the explorer-service. This service does more than the data-collector daemon, since it also provides historical information about the network.
We should stop using the data-collector daemon and replace it by hathor-p2p-monitor, since they do the same.
Currently we run a daemon called
data-collectorto collect the network state and save it in a Redis instance.This daemon is deployed independently from the main service, in a Docker container (see https://github.com/HathorNetwork/hathor-explorer-service/blob/main/Dockerfile)
However we now have a new service, hathor-p2p-monitor, that exposes an API that could be used to get the network information needed by the explorer-service. This service does more than the
data-collectordaemon, since it also provides historical information about the network.We should stop using the
data-collectordaemon and replace it by hathor-p2p-monitor, since they do the same.