item=30
total=70
percent=$(awk "BEGIN { pc=100*${item}/${total}; i=int(pc); print (pc-i<0.5)?i:i+1 }")
echo $percent
43
---
used = 30
total = 70
percentage=$(awk "BEGIN { pc=100*${used}/${total}; i=int(pc); print (pc-i<0.5)?i:i+1 }")",
echo $percentage
wk: BEGIN { pc=100*15/; i=int(pc); print (pc-i<0.5)?i:i+1 }
This is how I finally made sense of interfaces in Go. There are countless resources out there, but fails to simplify how to grasp and implement interfaces effectively, atleast for me. While observing my niece one day (toddlers can be surprisingly inspiring!), an analogy clicked in my mind. Let me
Cardinality refers to the number of unique elements in a set or the number of distinct values in a data set. In the context of metrics and time-series data, cardinality refers to the number of unique combinations of metric name, label name, and label value that are present in a
k8s_terraform_metrics/templates/k8s_provider.tf at main · ashwiniag/k8s_terraform_metricsTerraform + K8s + Vicoriametrics + Kube-state-metrics + Prometheus operator - ashwiniag/k8s_terraform_metricsGitHubashwiniag
Simple setup to monitor my machine using node_exporter: Exposes my machine metrics at http://localhost:9100/metrics vmagent: Scrapes the metrics exposed at /metrics at defined interval and sends it to victoriametrics victoriametrics: It is a single node set up, a tsdb storage. grafana: Visual representation of metrics used