Skip to content
eSHARS Operations

eSHARS Operations

eSHARS Operations

Infrastructure, runbooks, incidents, and operational knowledge for the eSHARS platform.

Day-to-day

Runbooks — Reusable step-by-step procedures. If you need to do X repeatedly, it lives here.

Monitoring — Job monitoring, alerts, and observability dashboards.

Incidents — Post-incident reports: what broke, timeline, root cause, lessons.

Investigations — Time-bound research into anomalies or unknowns.

Infrastructure & Configuration

Infrastructure — How Azure resources are configured: App Services, VMs, networking, storage.

Changes — One-time planned changes with scope, risk, and outcome. Proposed → approved → completed.

Decisions — Why things are configured the way they are. What was considered, what was rejected.

Pipelines — CI/CD pipeline architecture and troubleshooting.

Tooling & Access

Scripts — Azure Automation runbooks, SQL scripts, PowerShell utilities.

Database — Operational database queries, maintenance scripts, DNS alias swaps.

Credentials — Certificate and credential rotation procedures.

Variable Groups — Azure DevOps variable group documentation.

Security & Compliance

Security — Microsoft Defender posture, findings, and remediation runbooks.

Device Management — Azure AD join, offboarding, troubleshooting.

Key Distinctions

Runbook vs Change Record

A runbook is reusable — it describes how to perform an operation any time it needs doing (e.g., how to restart the job scheduler, how to roll back a deployment). A change record is a specific one-time event with a date, a scope, and an outcome (e.g., the prod SSRS VNet rollout on 2026-03-31). If you’re planning a specific piece of work, it’s a change record.

Incident vs Investigation

An incident is a production issue — something broke, users were affected. An investigation is proactive or reactive research that may or may not have user impact (e.g., diagnosing why reports weren’t loading, researching a performance anomaly). Investigations often precede or prevent incidents.

Infrastructure page vs Decision

An infrastructure page describes the current state of a resource (what it is, how it’s configured, known issues). A decision explains why it was configured that way — what alternatives were considered and why they were rejected. Decisions are permanent records; infrastructure pages are updated as the resource changes.

Quick Reference

  1. Check Incident Response
  2. Check Monitoring for active alerts
  3. Check Investigations for prior research on similar issues