microsoft/CSS-Exchange

[Feature Request] basic storage health checks for Healthchecker.ps1

Open

#1,379 opened on Dec 15, 2022

View on GitHub
 (0 comments) (0 reactions) (1 assignee)PowerShell (985 stars) (234 forks)batch import
Health CheckerNeed InvestigationNew Feature/CheckTriagegood first issuehelp wanted

Description

Is your request related to a problem? Please describe. A clear and concise description of what the problem is and the results it had on the environment.

given all the ways that storage issues can impact exchange service functionality it might make sense to implement some basic/quick storage health checks in the Healthchecker.ps1 script

Describe The Request A clear and concise description of the feature to add to a current tool or a new tool with what we all want to be checking with examples.

some basic checks that might be useful for heading off service outages

  • X% disk space free on any storage volume with mail queue
  • X% disk space free on any storage volume with a mailbox database or logs
  • X% disk space free on any storage volume with IIS logs

maybe some more optimization type checks along the lines of

  • X days of IIS/OWA related logs are present (maybe consider deletion after Y days0
  • N older OWA versions are present on a CAS server (maybe flag all versions that are now obsolete and can be deleted)

it might make sense to have a dedicated storage management script that could actually help with cleaning up exchange related volumes

  • log files older than X days
  • deleting older OWA versions no longer in use
  • flagging possible cruft files (e.g. old .RAW files, old databases or logs no longer in the active site configuration)

Additional context Add any other context or screenshots about the feature request here.

exchange servers can fail hard if storage gets exhausted and while there is no replacement for active monitoring, incorporating some basic checks that get scanned on each run of the healthchecker might be a way to flag some items before they get to a critical threshold

Contributor guide

Tech stack
None
Domain
infrastructureperformanceobservability
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic PowerShellExchange Server conceptsStorage monitoring
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Examine the existing Healthchecker.ps1 script in the repository to understand its structure and current health checks. Then, implement additional functions to check disk space on volumes containing mail queue, mailbox databases/logs, and IIS logs. Optionally, consider creating a separate storage management script for cleanup tasks like deleting old logs and obsolete OWA versions. The implementation should follow the existing pattern and include clear thresholds or configurable parameters.