Install the OpsVerse Agent

the opsverse agent can be installed in seconds on a variety of environments to begin sending your telemetry (metrics, logs, and traces) to your observenow backend this section will document how to install the agent on kubernetes , docker swarm , standalone linux machines , and standalone microsoft windows machines kubernetes monitoring a kubernetes cluster is as simple as running a helm chart command on the cluster getting started to collect metrics , logs , and traces from a kubernetes cluster and its applications, run the following command $ helm upgrade install devopsnow agent n devopsnow create namespace observe agent \\ \ repo https //registry devopsnow\ io/chartrepo/public \\ f \<path to opsverse values yaml file> following is an example values yaml file cluster name first cluster logs host \<logshost> username devopsnow password \<password> multiline snippet | \ multiline firstline '^\d{2,4}\\ \d{2,4}\\ \d{2,4} \d{2,4}\\ \d{2,4}\\ \d{2,4}\\ \d{1,6}' max lines 200 victoria metrics agent remotewriteurls \ https //\<metricshost>/api/v1/write extraargs remotewrite basicauth password \<password> remotewrite basicauth username devopsnow remotewrite label cluster=first cluster otelcollector enabled true jaeger url "https //\<traceshost>/api/v2/spans" auth "basic <`echo n 'devopsnow \<password>' | base64`>" single machine some workloads run on a single machine for example, a 64 bit linux vm you may also install the agent to collect metrics from that node ( and any subsequent https //prometheus io/docs/instrumenting/exporters/ you install on it ) for end to end observability to do so, simply run \# for amd64 machines $ curl l https //opsverse public s3 amazonaws com/agent/single node/installer sh o installer sh && chmod +x /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 \<password> you can then verify the agent is running $ sudo systemctl status opsverse agent if some other service is using the port 12345, you might get an error with opsverse agent logs as failed to start opsverse agent to resolve this error, go to /etc/systemd/system/opsverse agent service file and add this server http address=127 0 0 1 \<port> at the last of execstart command please replace the placeholder \<port> with port other than 12345 for example the /etc/systemd/system/opsverse agent service file should look like execstart= /usr/local/bin/opsverse telemetry agent config file=/etc/opsverse/agent config yaml config expand env server http address=127 0 0 1 12347 now restart the agent by using the command and this should resolve the issue $ sudo systemctl restart opsverse agent scrape additional targets some services already expose a /metrics endpoint that the agent can scrape and ship for the agent to automatically begin collecting those metrics, simply drop a json file inside /etc/opsverse/targets/ specifying where to scrape for example, you have a local etcd running, your file /etc/opsverse/targets/etcd json may look like \[ { "labels" { "job" "integrations/etcd" }, "targets" \[ "localhost 2379" ] } ] for services that don't expose a /metrics endpoint, we run prometheus exporters https //prometheus io/docs/instrumenting/exporters/ for those services and scrape those targets instead docker compose opsverse agents can be installed using docker compose structure download the opsverse agent zip file by using the command below and unzip it $ curl lo https //github com/opsverseio/installers/raw/main/opsverse agent zip $ unzip opsverse agent zip note you should have three files in the opsverse agent folder; env , docker compose yaml and agent/config/agent yaml configuration env is the only file you need to edit the editable variables in the env file can be found in your opsverse admin console after editing the variables in the env file, run the below command $ docker compose up d microsoft windows installing opsverse agent on machines running microsoft windows getting started to install opsverse agent on windows machine, follow the steps below download the opsverse agent windows installer zip https //github com/opsverseio/installers/raw/main/opsverse agent windows zip unzip the file open windows powershell as an administrator in the same path (i e inside the opsverse agent windows installer folder) and run the installation ps1 using the command /installation ps1 during the installation, the installer will ask, enter a unique hostname in the next step, the installer will ask the values of observenow metrics url, observenow logs url and the password you can find them in your opsverse admin console under observenow > integrations > urls and integration credentials that’s it the installer will set up and configure opsverse observenow agents to capture metrics from the windows instance once the setup is complete, you should be able to see your windows host machine in grafana, and start seeing machine specific metrics/logs flowing in " you should be able to see the services up and running in services msc under apps section of your observenow instance, click on grafana icon and go to the explore section to explore logs and metrics collected by the agent