Skip to main content
Alerting & Response/Alert Events

GetAlertNoiseAnalysisJob

Check the status and results of a noise analysis job

GET/api/v1/alerting/noise-analysis/{jobId}

Operation ID

GetAlertNoiseAnalysisJob

Since

1.0.0

Execution Mode

Synchronous

Auth Context

Auth Required

Auth Context

Send these values as request headers when calling this API.

AuthorizationstringRequired

Bearer Token

X-Tenant-IDstring

X-Tenant-ID

Request Inputs

Path Parameters

  • jobId
    StringRequired

    Job identifier to check status for

Responses

200 OK
200 OK

On success, this API returns the following response structure.

  • jobId
    String

    Unique identifier of the analysis job

    Example: job-001

  • status
    String

    Job status: pending, running, completed, or failed

    Example: completed

  • timeRange
    String

    Time range used for analysis

    Example: 7d

  • topK
    Integer

    Number of top noisy rules requested

    Example: 10

  • groupBy
    List

    Grouping fields used in analysis

    Example: item1,item2

  • tenantId
    String

    Tenant identifier for the analysis scope

    Example: 1

  • report
    Object

    Analysis report (populated when job completes)

    • generatedAt
      String

      Timestamp when the report was generated

      Example: 2026-01-15T08:00:00Z

    • timeRange
      String

      Time range covered by the report

      Example: 7d

    • topNoisyRules
      List

      Top noisy rules ranked by fire count

      Example: (nested array)

      • ruleId
        String

        Alert rule identifier

        Example: rule-abc123

      • ruleName
        String

        Alert rule name

        Example: Disk IO Warning

      • fireCount
        Integer

        Number of times the rule fired

        Example: 247

      • autoResolveRate
        Long

        Percentage of alerts that auto-resolved

        Example: 0.92

      • avgDurationSec
        Long

        Average alert duration in seconds

        Example: 45.5

      • severity
        String

        Severity level of the rule

        Example: warning

    • stormEvents
      List

      Alert storm events detected during the period

      Example: (nested array)

      • startTime
        String

        Start time of the storm event

        Example: 2026-01-15T08:00:00Z

      • durationMin
        Integer

        Duration of the storm in minutes

        Example: 15

      • alertCount
        Integer

        Number of alerts in the storm

        Example: 120

      • rootRuleId
        String

        Root cause rule identifier

        Example: rule-abc123

    • suppressionSuggestions
      List

      Suggested suppression actions for noisy rules

      Example: (nested array)

      • ruleId
        String

        Rule identifier for the suggestion

        Example: rule-abc123

      • ruleName
        String

        Rule name for the suggestion

        Example: Disk IO Warning

      • suggestedAction
        String

        Suggested action (e.g. increase_threshold, add_silence, disable)

        Example: increase_threshold

      • reason
        String

        Explanation for why this action is suggested

        Example: 92% of alerts auto-resolve within 60 seconds

    • status
      String

      Report generation status

      Example: completed

    • analyzedEventCount
      Integer

      Total number of alert events analyzed

      Example: 1500

    • analysisDurationMs
      String

      Duration of the analysis in milliseconds

      Example: 1200

  • createdAt
    String

    Timestamp when the job was created

    Example: 2026-01-15T08:00:00Z

  • completedAt
    String

    Timestamp when the job completed

    Example: 2026-01-15T08:00:00Z

  • durationMs
    String

    Duration of the analysis in milliseconds

    Example: 1500

  • errorMsg
    String

    Error message if the job failed

    Example: request timeout