LeanSentry: IIS Application Monitoring + Diagnostics

Showing 25 of 32 from the live probe.

• Get Report Root Cause

  Gets detailed information about a specific root cause (classified root cause pattern), including example stack traces and full matching details. Use the root_cause_id from ListReportRootCauses or from the report summary.

• List Applications

  Gets a paginated list of applications in an environment with summary metrics. Each application includes a TopIssues preview (top issues by severity, plus issues with diagnostics). Use this to see what applications have significant issues, and which have diagnostic information, before calling GetIssueDetailsInApplication. You can also call GetApplication for complete application details.

• Get Report Tree Dataset

  Gets a hierarchical tree dataset by name. Tree datasets represent structures like thread stacks, async task trees, or memory object graphs with parent-child relationships.

• Get Report Summary

  Call this first! Gets the summary and contents for a specific diagnostic report. The Summary field contains the basic details. The report metadata lists available details you should use for further analysis, including report sections, conditions identified, metrics, datasets, and debug logs. We also include some preliminary assessments and issue classifications generated from this report, but these should be taken with a grain of salt. Prioritize inspect this report's details for a complete root

• Get Report Metric

  Gets a specific performance metric by name with detailed statistics including average, percentiles and histogram data, and recent value history leading up to the incident. Get metric names from ListReportMetrics.

• Get Report Section

  Gets the full content of a specific section in the diagnostic report. Use section names from GetReportSummary or GetReportMetadata.

• Get Application

  Gets detailed information for a specific application, including all issues affecting that application. Use this to drill down into a specific application's health and issues, then call GetIssueDetailsInApplication on the issues of interest. Issues with diagnostic information (root causes, and diagnostic repots) can be fixed.

• List Environments

  Lists all environments accessible to the current account, with a ~30-day rolled-up view for each. Use this to discover available environments and their overall health before drilling into a specific one with GetEnvironment. NOTE: This command does not provide information on specific issues and diagnostics available in each environment, call GetEnvironment on the specific environment on the basis of overall traffic, or high other level metrics, or ask the user which environment they care about. A

• List Recent Reports

  Lists your recent diagnostic reports. Returns summaries with report IDs to pass to GetReportSummary. If sessionId is provided, lists reports for that specific session only. Otherwise, lists reports from all sessions you have access to. IMPORTANT: If the user asks for more reports, use the 'count' and 'skip' parameters to retrieve and paginate through more repots than loaded by default.

• Search Report Log

  Searches a log file for keywords and returns matching lines with surrounding context. Useful for finding specific errors, thread states, or patterns in large logs without reading the entire content. HINT: You can search specific sections of the log (get section names from GetReportLogIndex) or their line subsets, and paginate through search results. Hint: you can use total number of search matches for a search to quickly count matching frames in a very long stack trace without actually reading i

• List Report Root Causes

  Lists root causes (classified root cause patterns) that were classified in this diagnostic report. This can help see if the root cause seen in this report has happened across other diagnostic reports. Returns compact summaries showing matched patterns and their characteristics.

• List Report Logs

  Lists all available logs (debug logs, diagnostic output) for a report with metadata including log section index, line counts, and descriptions. The logs can provide the deepest level of information for troubleshooting if the other information is not sufficient. Use this to discover what logs are available, then call GetReportLogIndex to get the log details including available sections, so you can read specific log parts of interest (logs can be long).

• List Report Metrics

  Lists all available performance metrics for a diagnostic report, including primary impact metrics and other system and application performance metrics collected. Use this to assess impact and performance conditions observed with the report. Call GetReportMetric to get the statistical and recent history data stored on the metric.

• Set Issue Diagnostic Setting

  Sets a specific diagnostic setting for an issue to tune how diagnostics execute. IMPORTANT: Use this only when diagnostics are failing to complete, timing out, or you need to adjust detection thresholds based on what ConfigureIssueDiagnostics shows. Always call ConfigureIssueDiagnostics first to see available settings, their defaults, and currently configured values before modifying. Pass settingName exactly as shown in the Settings list. Pass value as a string matching the setting type shown —

• Read Report Log

  Reads a log file with optional filtering by section name and line range. Enables targeted access to specific parts of large logs (e.g., specific debugger commands in debug logs). Returns plain text content. HINT: Use GetReportLogIndex to read just the sections of the log you want, and/or use SearchReportLog to find what you want in a section or count search matches without reading large parts of the log.

• Get Diagnostic Budget For Issue In Application

  Gets information on diagnostic budget consumption on the server, and this issue in a specific application. This can be used to help understand budget constraints as a reason for why diagnostics for a specific issue may be limited or failing (based on diagnostic stats from ConfigureIssueDiagnosticsInApplication). Shows diagnostic attempts, diagnostic impact (CPU time, debugger pause time) by target and diagnostic type. Diagnostic budgets constrain diagnostics both at the server (total impact) and

• Configure Issue Boost Level

  Reads or sets diagnostic boost points for a specific issue (or cause/contributor). Boost points temporarily inflate the diagnostic budget for a target without changing detection thresholds or globally increasing diagnostic frequency. Use this when diagnostics are failing to complete due to budget exhaustion (as reported by get_diagnostic_budget_for_issue_in_application or configure_issue_diagnostics), and you want to give the issue more room to complete — without lowering the intent threshold an

• Get Root Cause Details

  Gets complete diagnostic details for a specific root cause, including full stack traces and all diagnostic details available. Use this when you need to investigate or fix a specific root cause. Call this after GetIssueDetailsInApplication identifies root causes. If you don't have an applicationId, you can omit it and the tool will search all applications affected by the issue.

• Configure App Diagnostics

  Reads or sets per-app diagnostic configuration, including DiagnosticProfile and Importance, to allow more or fewer diagnostics in the application relative to others. These are an application-wide settings that apply to all issues in the app — use configure_issue_diagnostics to configure individual issue diagnostics. DiagnosticProfile controls how proactively we diagnose the application: None=no diagnostics, Conservative=severe issues only, Balanced=default, Proactive=proactively diagnosing norma

• Get Report Log Index

  Gets the log file index if available. Enables targeted access to specific parts of large logs using section index (e.g., specific debugger commands in debug logs).

• List Contributors For Issue Cause

  For issues with contributors, lists contributors for a specific issue cause, sorted by impact (with pagination support). Use this after GetIssueDetailsInApplication to explore contributors beyond the initial subset of those that were diagnosed or were top by impact. By default (detailed=false), returns a compact one-line text format for efficient discovery of high-impact or diagnosed contributors. Use detailed=true with pagination to get full contributor objects with all metrics, root causes, an

• Get Issue Details In Application

  Gets detailed information for a specific issue in a specific application, including all causes, contributors, metrics, root causes, and recent diagnostic reports. Use this to drill down into a specific issue to understand what's causing it and how to fix it.

• Track Possible Issue Fix

  IMPORTANT: Call this tool when you present a fix or solution to the user, or proceed with a fix. Records a solution attempt for a diagnostic report. LeanSentry will then track whether this issue recurs in production to validate the solution — this is valuable feedback for the user.

• Get Report Assessment

  Gets the full content of a specific assessment. Returns the assessment with its content populated. Take these with a grain of salt, and confirm it with your own analysis of the report details.

• Get Report List Dataset

  Gets a flat list dataset by name. List datasets represent sequential data like stack traces, finalization queue entries, or log entries without hierarchical structure.