But I do it to read Manga and laze around almost every where. That's why I try to write everything about servers and their stupid troubles.
Knowledge is Power!
Why nslookup works but ping says “Name or service not known”? Let’s get basic terminology straight up and it’s assumed you already understand how DNS resolution works. In my quest to understand how tools like nslookup and ping behave differently, I was honestly confused by the terms DNS
Knowledge is Power!
In my experience, I've revisited this topic multiple times and every single time, I’ve learned something new. So here’s a simple visual walkthrough for those who want to understand what really happens when you type a domain name into your browser. We’ll break this into
Knowledge is Power!
In Go, there are several ways to allocate and initialize memory. Pre-requisite: undertsand types in Go var Declaration When you declare a variable using var: var x int var s string var m map[string]int var sl []int * The variable is zero-valued (0 for numeric types, "" for
Knowledge is Power!
Primitive Types Primitive types (also called basic types) are the simplest, fundamental data types that aren't composed of other types: * Numeric types: * Integers: int, int8, int16, int32, int64, uint, uint8, etc. * Floating-point: float32, float64 * Complex: complex64, complex128 * Boolean type: bool * String type: string These types store their values
Knowledge is Power!
In my current organization, I wrote a helper script long back to organize and set up Kubernetes contexts across multiple GCP projects and environments, with custom naming based on cluster labels. I also created another script to handle all EKS clusters across AWS regions using a specified AWS SSO profile.
Knowledge is Power!
We’ve been building gokakashi in Go for a while now, and we had this wild thought: “What if users could define their own evaluation conditions on top of the scan reports?” Something like this in the config file: check: condition: | sev.critical > 0 || sev.high > 0 &
Knowledge is Power!
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
Knowledge is Power!
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
Knowledge is Power!
Bits are simply 0s and 1s and that's all the language our machine understands. But in larger picture how do we understand this when we are programming? Trying to troubleshoot production system? 8 bits = 1 byte * Bit: The smallest unit of data in computing, representing either a 0
Knowledge is Power!
k8s_terraform_metrics/templates/k8s_provider.tf at main · ashwiniag/k8s_terraform_metricsTerraform + K8s + Vicoriametrics + Kube-state-metrics + Prometheus operator - ashwiniag/k8s_terraform_metricsGitHubashwiniag
Knowledge is Power!
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
Knowledge is Power!
k8s_terraform_metrics/templates/ssm.tf at main · ashwiniag/k8s_terraform_metricsTerraform + K8s + Vicoriametrics + Kube-state-metrics + Prometheus operator - ashwiniag/k8s_terraform_metricsGitHubashwiniag