Issue Details

Details of an issue

This page shows full context and actions for a single issue.

Top: Title and description

  • Title: the issue title (often the predicate name for policy-generated issues).
  • Description: a short statement of the failing condition. Example: “free_percent is 11, should be 20”.

Metadata

  • Created: timestamp when the issue was opened.
  • Instance: the SQL Server instance the issue refers to.
  • Database / Object: the database or object name when applicable.

Explanation and remediation

  • A concise explanation describes why the issue matters and recommended remediation steps. Include practical suggestions (for example: clear old files, adjust backup/retention policies, increase disk capacity, or change maintenance windows) and links to relevant documentation or runbooks.

Metric chart

  • A time-series chart displays the metric evaluated by the predicate (for example, available disk space) over the selected interval. The chart shows values up to and including the point when the predicate was evaluated so you can see trend leading to the violation.

Policy evaluation details

  • “Show Policy Evaluation Details” reveals the full evaluation record for the predicate: input properties, threshold values, measured value, evaluation timestamp, policy name, predicate id, and any additional diagnostic fields.
  • Use this to verify the exact inputs that produced the issue.

Tags

  • The Tags control lists tags assigned to the issue and lets you add or remove tags for workflow or routing (for example: “ops”, “storage”, “urgent”).

Closing notes

  • Enter free-form notes describing how the issue was investigated or fixed.
  • Notes are stored with the issue for audit and postmortem purposes.

Actions

  • Save: persists tag changes and closing notes without changing issue state.
  • Close issue: manually closes the issue. If the underlying predicate still fails on a subsequent automated evaluation, a new issue will be opened.
  • Exclude: opens a dialog to disable this predicate for the specific instance/database/object/group/tag combination. The dialog also offers the option to close all matching issues for the selected scope. Use exclusions sparingly and document the rationale (ex. test instance).
  • Fix issue: when available, this button schedules an automated remediation job that executes the predefined T-SQL script associated with the predicate. Not all issues support automatic fixes — availability depends on the predicate and the remediation defined for it. The jobs UI shows the script to be run, required permissions, and the scheduled job status. Execution logs and results are recorded with the job.

Behavior and history

  • Closed issues remain available for historic review; use filters on the Issues list to include closed items.