Splunk SPLK-1002: SPL Stats, Eval, and Transformations
SPL becomes analytically powerful when searches move beyond matching events and begin calculating, grouping, and reshaping them. The `eval` command creates or transforms…
Read article03 / THE LATESTFresh thinking
From the editorial desk.
New technical explainers, certification perspectives and practical ideas.
NVIDIA NCA-AIIO: Observability for GPU Infrastructure
GPU infrastructure needs observability at several layers: device health, utilization, memory behavior, power and thermals, PCIe and NVLink traffic, node resources, scheduler state,…
Read articleNVIDIA NCA-AIIO: Power, Cooling, and Capacity for AI Systems
AI infrastructure pushes data-center power density and cooling design far beyond conventional server planning. Modern GPU systems can consume tens of kilowatts per…
Read articleSplunk SPLK-5001: CIM and Data Models for Security Analytics
The Splunk Common Information Model, or CIM, provides a vendor-neutral field and tag vocabulary for common data domains such as authentication, network traffic,…
Read articleSplunk SPLK-5001: Building Security Detections in Splunk
Within the Splunk security platform, a security detection is a repeatable analytical rule that identifies behavior worth investigating. In Splunk, detections typically begin…
Read articleSplunk SPLK-1002: Useful Splunk Dashboards
A useful Splunk dashboard is not a collection of every metric a team can display. It is a decision surface that helps a…
Read articleSplunk SPLK-1002: Lookups, Tags & Event Types in Splunk
Splunk knowledge objects let teams add reusable meaning to indexed events without changing the raw data. Lookups enrich events with external reference information,…
Read articleSplunk SPLK-1001: SPL Search Commands for Analysts
Splunk Search Processing Language, or SPL, turns indexed events into answers. Analysts use search terms to narrow data, field commands to shape events,…
Read articleSplunk SPLK-1001: How Splunk Indexing and Search Work
Splunk’s core workflow has two broad phases: events are ingested, parsed, indexed, and stored; later, users search those indexed events and transform results…
Read articleSplunk SPLK-1001: Fields, Extractions & Knowledge Objects
Splunk events become much more useful when raw text is enriched with fields and reusable knowledge. Fields let searches refer to meaningful values…
Read articleSplunk SPLK-1003: Data Ingestion and Sources
Splunk becomes useful only after data reaches the platform with enough structure and context to support search, alerting, dashboards, and security analytics. Ingestion…
Read articleSplunk SPLK-1003: Indexes & Data Retention
Splunk indexes are the storage and search boundary for ingested events. An index contains buckets that move through lifecycle states as data ages,…
Read articleSplunk SPLK-1003: Forwarders & Distributed Architecture
Splunk Enterprise scales by separating data collection, indexing, search, and management responsibilities across components. Forwarders collect data from source systems and send it…
Read articleHashiCorp Terraform Associate 004: Terraform Secrets Management
Terraform often needs sensitive values to authenticate providers, configure applications, bootstrap databases, or connect managed services. The safest design minimizes how many secrets…
Read articleHashiCorp Terraform Associate 004: Terraform Policy as Code
Policy as code applies organizational rules to infrastructure changes automatically. Instead of relying on reviewers to remember every tagging, networking, encryption, region, and…
Read article