# Native Synthetic outage severity needs to be changed from SEV-3 to SEV-1/SEV-2

**URL:** <https://community.dynatrace.com/t/native-synthetic-outage-severity-needs-to-be-changed-from-sev-3-to-sev-1-sev-2/57130>\
**Category:** Synthetic Monitoring\
**Tags:** dynatrace-saas, synthetic-monitoring\
**Created:** [October 12, 2026, 11:32am UTC](https://community.dynatrace.com/t/native-synthetic-outage-severity-needs-to-be-changed-from-sev-3-to-sev-1-sev-2/57130 "2026-10-12T11:32:08Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Stusharranjan1](https://avatars.discourse-cdn.com/v4/letter/s/91b2a8/32.png) [@Stusharranjan1](https://community.dynatrace.com/u/Stusharranjan1)\
**Post date:** [October 12, 2026, 11:32am UTC](https://community.dynatrace.com/t/native-synthetic-outage-severity-needs-to-be-changed-from-sev-3-to-sev-1-sev-2/57130/1 "2026-10-12T11:32:08Z")

</div>

Hi all,

I am testing severity behavior for native Dynatrace Synthetic HTTP/Browser outage problems in Latest Dynatrace.

For business-critical production URLs, the requirement is that a sustained outage should be treated as SEV-1 or SEV-2 based on business criticality.

In my test environment I reproduced the following:

Native HTTP Synthetic global outage:  
- event.provider = SYNTHETIC  
- event.type = HTTP\_CHECK\_GLOBAL\_OUTAGE  
- event.severity = 3  
- Problem severity = Minor (SEV-3)

The monitor also has Primary Grail Tags such as:  
- Environment = PROD  
- Criticality = Tier1  
- Application = test application

These tags are present on the generated event, but the native Synthetic event remains SEV-3.

I also tested a custom alert based on the Synthetic availability metric and set:

event.severity = 1

This successfully created a Critical (SEV-1) problem.

My questions are:

1. Is there any supported way to change event.severity for the native Synthetic HTTP/Browser outage event itself?

2. Can severity be configured per Synthetic monitor?

3. Can Primary Grail Tags or other metadata be used to make business-critical PROD Synthetic outages SEV-1/SEV-2?

4. Can native Synthetic events be processed through Davis Events OpenPipeline to override event.severity?

5. If native Synthetic severity cannot be changed, what is the recommended design to avoid having both:  
- native Synthetic SEV-3 problem  
- custom SEV-1/SEV-2 problem  
for the same outage?

The use case is business-critical customer-facing URLs where Synthetic availability is a high-priority monitoring signal.

Thanks.