Download the GCM wget “https://github.com/git-ecosystem/git-credential-manager/releases/download/v2.5.0/gcm-linux_amd64.2.5.0.deb” -O /tmp/gcmcore.deb Execute the installable file sudo dpkg -i /tmp/gcmcore.deb Configure GCM git-credential-manager configure Configure the GCM store git config –global credential.credentialStore plaintext or export GCM_CREDENTIAL_STORE=plaintext
Prerequisites Azure Subscription: Ensure you have an active Azure subscription. Azure AD Directory: You must have an Azure AD directory. User Permissions: Ensure you have permissions to create and manage resources in the Azure portal. Step-by-Step Guide Step 1: Create and Configure the Virtual Network Gateway Create a Virtual Network: …
Log in to your Grafana dashboard at PUBLICIP:3000. In another tab, go to the Grafana dashboard website. Search for the “Node Exporter Full” dashboard, and copy the dashboard ID. Back on your Grafana instance, select the plus sign on the side menu and click Import. Paste in the dashboard ID. Create a new …
Install the prerequisite package: sudo apt-get install libfontconfig Download and install Grafana using the .deb package provided on the Grafana download page: wget https://dl.grafana.com/oss/release/grafana_5.4.3_amd64.deb sudo dpkg -i grafana_5.4.3_amd64.deb Ensure Grafana starts at boot: sudo systemctl enable –now grafana-server Access Grafana’s web UI by going to IPADDRESS:3000. Log in with the username admin and the password admin. Reset …
Open the Alertmanager configuration: $ sudo $EDITOR /etc/alertmanager/alertmanager.yml Set the default route’s repeat_interval to one minute and update the receiver to use our Slack endpoint: route: receiver: ‘slack’ group_by: [‘alertname’] group_wait: 10s group_interval: 10s repeat_interval: 1m Create a secondary route that will send severe: page alerts to the Slack receiver; group by the team label: route: …
Go to slack.com and create a new workspace, following the step-by-step instructions on screen until you are given your workspace. Be sure to add a prometheus channel! From your chat, use the workspace menu to go to Administration and then Manage apps. Select Build on the top menu. Press Start Building, then Create New App. Give your application a name, and …
Now that we have a recording rule, we can build our alerting rule based on this. We know we want to alert when we have less than 75% of our application containers up, so we’ll use the job:uptime:average:ft < .75 expression: groups: – name: uptime rules: – record: job:uptime:average:ft expr: avg without …
Create the alertmanager system user: sudo useradd –no-create-home –shell /bin/false alertmanager Create the /etc/alertmanager directory: sudo mkdir /etc/alertmanager Download Alertmanager from the Prometheus downloads page: cd /tmp/ wget https://github.com/prometheus/alertmanager/releases/download/v0.16.1/alertmanager-0.16.1.linux-amd64.tar.gz Extract the files: tar -xvf alertmanager-0.16.1.linux-amd64.tar.gz Move the binaries: cd alertmanager-0.16.1.linux-amd64 sudo mv alertmanager /usr/local/bin/ sudo mv amtool /usr/local/bin/ Set the ownership of the binaries: sudo …
Using the expression editor, view the uptime of all targets: up Since we don’t want to alert on each individual job and instance we have, let’s take the average of our uptime instead: avg (up) We do not want an average of everything, however. Next, use the without clause to ensure we’re not …
Importing the library & requiring it Move into the forethought directory: cd forethought Install the prom-client via npm, Node.js’s package manager: npm install prom-client –save Open the index.js file, where we’ll be adding all of our metrics code: vim index.js Require the use of the prom-client by adding it to our variable list: var express = require(‘express’); var bodyParser …
Launch cAdvisor: $ sudo docker run \ –volume=/:/rootfs:ro \ –volume=/var/run:/var/run:ro \ –volume=/sys:/sys:ro \ –volume=/var/lib/docker/:/var/lib/docker:ro \ –volume=/dev/disk/:/dev/disk:ro \ –publish=8000:8080 \ –detach=true \ –name=cadvisor \ google/cadvisor:latest List available containers to confirm it’s working: $ docker ps Update the Prometheus config: $ sudo $EDITOR /etc/prometheus/prometheus.yml – job_name: ‘cadvisor’ static_configs: – targets: [‘localhost:8000’] Restart …
File system metrics contain information about our mounted file systems. These metrics are taken from a few different sources, but all use the node_filesystem prefix when we view them in Prometheus. Although most of the seven metrics we’re provided here are fairly straightforward, there are some caveats we want to address — the first …
Run stress -m 1 on your server before starting this lesson. When it comes to looking at our memory metrics, there are a few core metrics we want to consider. Memory metrics for Prometheus and other monitoring systems are retreived through the /proc/meminfo file; in Prometheus in particular, these metrics are prefixed with node_memory in the …