You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
prometheus v.: 2.48.0 | Hello. While the present repository is source of acquisition of the Prometheus and node_exporter program codes, related documentation's instructions at prometheus.io for stopping them within a terminal do not exist. However communicating how stopping is as relevant as starting since what starts must be able to be stopped.
p.s.: By experience, I learned that closing each terminal session in which these applications were started does end up the process that is attached to node_exporter but not the one that is attached to Prometheus, which is as sub-process of /usr/lib/systemd/systemd --user.
The text was updated successfully, but these errors were encountered:
Both are in prometheus/prometheus itself and not in this repo (prometheus/docs).
node_exporter is in its own repo, with some documentation there.
AFAIK you can gracefully shutdown all binaries in the Prometheus project by sending a SIGTERM/SIGINT, which can be done by pressing Ctrl-C in a terminal. I would say that is common knowledge how to start and stop programs with your preferred OS, and not specific to Prometheus.
Usually, you will run processes like the Prometheus server or the node_exporter from some kind of service manager, like systemd on a Linux server, SysV init on older Linux or UNIX systems, Kubernetes in the cloud, etc. But each of these have their own usage, and we cannot really document all of them on the Prometheus doc page, and Prometheus just behaves like any other program under these service managers. Nothing specific here.
prometheus v.: 2.48.0 | Hello. While the present repository is source of acquisition of the Prometheus and node_exporter program codes, related documentation's instructions at prometheus.io for stopping them within a terminal do not exist. However communicating how stopping is as relevant as starting since what starts must be able to be stopped.
p.s.: By experience, I learned that closing each terminal session in which these applications were started does end up the process that is attached to node_exporter but not the one that is attached to Prometheus, which is as sub-process of
/usr/lib/systemd/systemd --user
.The text was updated successfully, but these errors were encountered: