Read blocked requests in KQL, qualify false positives and apply targeted rules with evidence.
Cloud · Infrastructure · Automation · AI
Operational knowledge for technical systems.
Naxaya turns architecture choices, failure modes, implementation patterns and runbook-level checks into practical technical notes for teams that need systems to stay explainable after deployment.
naxaya.field-notes operational view
DNS, Private Endpoint, Application Gateway and validation matrices.
Automation guardrails, restore checks, identity troubleshooting and handover notes.
Evidence before exception Validation before rollout Runbook before incident
Incident of the day A private AI agent can act but nobody can explain the action
Open diagnosis Symptom: A private AI agent can act but nobody can explain the action. First checks: List approved sources · Trace tool calls.
01
Architecture that can be operated
Design choices are written with their constraints, validation commands, failure modes and return paths.
02
Automation with guardrails
AWX, Ansible and scripts are treated as operational interfaces, not just convenient execution buttons.
03
Private AI with controls
Agent workflows stay grounded in approved sources, scoped identities, observable actions and human validation.
Focused series
Operational paths, grouped by problem.
Each series follows a concrete path from the initial symptom or design choice to validation, guardrails and production-ready runbooks.
Latest articles
Azure Functions: diagnose a private HTTP endpoint before changing code
Build an operational runbook for private Azure Functions failures by separating DNS, Private Endpoint, access restrictions, private storage, Application Insights logs and rollback evidence.
Read articleKQL snippet: correlate an Azure Functions private HTTP endpoint
A short query to separate DNS, private access, Functions runtime and application exceptions during a private HTTP incident.
Read articleAzure AKS: diagnose private ingress before changing deployments
Build an operational runbook for AKS private ingress failures by separating DNS, Application Gateway, ingress controller, Kubernetes service endpoints, pod readiness and rollback evidence.
Read articleKQL snippet: correlate AKS private ingress and application logs
A short query to read ingress controller and application logs together when a private AKS route returns 502, timeouts or no endpoints.
Read article