microsoft / microsoft/CSS-Exchange

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

Open
#1,379 0 comments 0 reactions 1 assignee View on GitHub

@dpaulson45 is already working on this.

Since Dec 6, 2024.

good first issue Health Checker help wanted Need Investigation New Feature/Check Triage
Dominant language
PowerShell
Stars
1.3k
Forks
395
Avg merge
14h 7m
Merged PRs (30d)
5

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.