↳ GitHub sourceAnalytics ruleHigh

Atlassian Beacon Alert

Description

'The analytic rule creates an incident when an alert is created in Atlassian Beacon. The incident's events contains values such as alert name, alert url, actor name, actor details, worskpace id of the atlassian beacon, etc. Navigate to the alertDetailURL to view more information on recommendations and remediations.'

Rule type: Scheduled
Version: 1.0.1
Declared status: Available
Query frequency: 5m
Query period: 5m
Trigger: gt 0

Declared sources

Metadata from the source file. No dependencies inferred from KQL.

Connectors

AtlassianBeaconAlerts

Data types

atlassian_beacon_alerts_CL

KQL query

Original query, unchanged.

atlassian_beacon_alerts_CL
| project TimeGenerated, detectiontime_d, alert_created_t, alert_title_s, alertTitle_s, alert_url_s, alertDetailURL_s, activity_action_s, alert_product_s, activity_subject_ari_s, actor_name_s, actor_url_s, actor_sessions_s, atlassianAlertType_s, atlassianWorkspace_id_g, atlassianWorkspace_orgId_s, Type

Source provenance

GitHub

Displayed values come from files in Azure/Azure-Sentinel. They describe the published template, not your workspace configuration.

File: Solutions/Integration for Atlassian Beacon/Analytic Rules/AtlassianBeacon_High.yaml ↗
Commit: 9800e51 ↗
Source identifier: 83fbf6a2-f227-48f4-8e7b-0b0ecac2381b

Additional source files 2

Solutions/Integration for Atlassian Beacon/Analytic Rules/AtlassianBeacon_High.yamlsource ↗Solutions/Integration for Atlassian Beacon/Data/Solution_AtlassianBeacon.jsonsolution-membership ↗

GSTEP / CATALOG TRACKING

Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC

GSTEP sync dates, separate from the source content’s publication dates.