Individual VMs

opsverse's single node agent can be used to collect metrics from individual vms install and run download and run the agent installer on the machine you wish to install the agent \# for amd64 machines $ curl l https //opsverse public s3 amazonaws com/agent/single node/installer sh o installer sh \# for arm64 machines $ curl l https //opsverse public s3 amazonaws com/agent/single node/installer arm64 sh o installer sh chmod +x /installer sh sudo /installer sh m \<metricshost> l \<logshost> t \<traceshost> p if your machine already has the /etc/opsverse/agent config yaml file, the installer will prompt you to choose whether to overwrite it or to use the exiting one for no prompt (e g , in scripts), you may pass the f option to force the override the existing file alternatively, you can pass in no config override to use the existing config without prompting if both options are used together, no config override takes priority verify the agent is running $ sudo systemctl status opsverse agent at this point, you should be able to see metrics and logs coming into your observenow instance updating configurations there may be cases where you have to update the agent config file (at /etc/opsverse/agent config yaml ) for example, when you're adding a new log dir to forward or if you're updating backend credentials in those cases, after config update, simply restart the agent $ sudo systemctl restart opsverse agent collecting container metrics if your node has containers running on it, it's best to install cadvisor https //github com/google/cadvisor so that the agent can scrape the container metrics exposed by it as well you can do so by running the following on any 64 bit linux machine \# for amd64 $ curl https //raw\ githubusercontent com/opsverseio/installers/main/prometheus exporters/install exporter amd64 sh | sudo bash s e cadvisor \# for arm64 $ curl https //raw\ githubusercontent com/opsverseio/installers/main/prometheus exporters/install exporter arm64 sh | sudo bash s e cadvisor this will drop the resulting scrape target into /etc/opsverse/targets/ , so the agent will begin automatically scraping to view a convenient dashboard, you may import the grafana dashboard id 11600 (ensure you select the metricsserver datasource when prompted) collecting application traces if your machine has applications running on them, you can instrument them with your favorite open tracing libraries (e g , opentelemetry https //opentelemetry io/docs/instrumentation/ ), to begin sending them to your observability backend! to begin seeing these traces, install the opentelemetry collector on your 64 bit linux machine \# for amd64 $ curl https //raw\ githubusercontent com/opsverseio/installers/main/prometheus exporters/install exporter amd64 sh | sudo bash s e opsverse otelcontribcol \# for arm64 $ curl https //raw\ githubusercontent com/opsverseio/installers/main/prometheus exporters/install exporter arm64 sh | sudo bash s e opsverse otelcontribcol you may optionally pass the traces collector url, user, and password (found in the admin console under "urls and integrations") via the t , u , and p flags, respectively for any changes to the config at /etc/opsverse/exporters/opsverse otelcontribcol/config yaml , restart the opentelemetry collector sudo systemctl restart prom opsverse otelcontribcol exporter you may view application integrations https //docs opsverse io/opentelemetry operator for kubernetes for tips on how to instrument apps to emit traces