# Mute 302 response code from failure detection

**URL:** <https://community.dynatrace.com/t/mute-302-response-code-from-failure-detection/49186>\
**Category:** Alerting\
**Tags:** problem-detection\
**Created:** [December 4, 2024, 7:31am UTC](https://community.dynatrace.com/t/mute-302-response-code-from-failure-detection/49186 "2024-12-04T07:31:51Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![suryansh21](https://avatars.discourse-cdn.com/v4/letter/s/e95f7d/32.png) [@suryansh21](https://community.dynatrace.com/u/suryansh21)\
**Post date:** [December 4, 2024, 7:31am UTC](https://community.dynatrace.com/t/mute-302-response-code-from-failure-detection/49186/1 "2024-12-04T07:31:51Z")

</div>

Hi ,

Actually my client is having very specific requirement, they don’t want any alert for response codes related to redirection for ex: 302 , How can I mute this response so that It won’t be considered as failed. Or they will not be receiving alert for this response code.

---

<div class="post-metadata">

**Author:** ![erh\_inetum](https://avatars.discourse-cdn.com/v4/letter/e/48db29/32.png) [@erh\_inetum](https://community.dynatrace.com/u/erh_inetum)\
**Post date:** [December 5, 2024, 7:19am UTC](https://community.dynatrace.com/t/mute-302-response-code-from-failure-detection/49186/2 "2024-12-05T07:19:31Z")

</div>

Hi&nbsp;[@suryansh21](https://community.dynatrace.com/user/80497)&nbsp;,

You can create [Failure Detection Rules](https://docs.dynatrace.com/docs/shortlink/service-failure-detection)

 ![erh_inetum_0-1733382894595.png](https://global.discourse-cdn.com/dynatrace/original/3X/6/1/61262c8eff1434b3f868616a91d68baaa58dbfb1.png)

First creating a Failure detection parameter:

 ![erh_inetum_1-1733383052244.png](https://global.discourse-cdn.com/dynatrace/original/3X/d/1/d1466fd5c8ce7e8759f7fbbc161789a42aa8c789.png)

And then associating the rule with the&nbsp;Failure detection parameter previously created:

 ![erh_inetum_2-1733383096751.png](https://global.discourse-cdn.com/dynatrace/original/3X/5/e/5e9000b7e473451407adfbad678c7b66c827965f.png)

Hope it helps.

Regards,

Elena.

---

<div class="post-metadata">

**Author:** ![suryansh21](https://avatars.discourse-cdn.com/v4/letter/s/e95f7d/32.png) [@suryansh21](https://community.dynatrace.com/u/suryansh21)\
**Post date:** [December 5, 2024, 10:30am UTC](https://community.dynatrace.com/t/mute-302-response-code-from-failure-detection/49186/3 "2024-12-05T10:30:59Z")

</div>

Thanks Elena for answering, so by doing this will it mute the response code 302 from failure detection ???

---

<div class="post-metadata">

**Author:** ![erh\_inetum](https://avatars.discourse-cdn.com/v4/letter/e/48db29/32.png) [@erh\_inetum](https://community.dynatrace.com/u/erh_inetum)\
**Post date:** [December 5, 2024, 10:34am UTC](https://community.dynatrace.com/t/mute-302-response-code-from-failure-detection/49186/4 "2024-12-05T10:34:15Z")

</div>

Welcome.

Yes, look at this paragraph in&nbsp;&nbsp;[Failure Detection Rules](https://docs.dynatrace.com/docs/shortlink/service-failure-detection)&nbsp;documentation:

“When Dynatrace detects a service error, it doesn’t necessarily mean that you want to label a request as failed. If the default service-error detection settings don’t meet your needs, you can configure failure detection settings as explained in this page.”

Hope it helps.

Regards,

Elena.

---

<div class="post-metadata">

**Author:** ![suryansh21](https://avatars.discourse-cdn.com/v4/letter/s/e95f7d/32.png) [@suryansh21](https://community.dynatrace.com/u/suryansh21)\
**Post date:** [December 5, 2024, 10:41am UTC](https://community.dynatrace.com/t/mute-302-response-code-from-failure-detection/49186/5 "2024-12-05T10:41:26Z")

</div>

ok got it Elena , so the steps that you suggested in the snaps will mute the 302 response code?

---

<div class="post-metadata">

**Author:** ![erh\_inetum](https://avatars.discourse-cdn.com/v4/letter/e/48db29/32.png) [@erh\_inetum](https://community.dynatrace.com/u/erh_inetum)\
**Post date:** [December 5, 2024, 10:50am UTC](https://community.dynatrace.com/t/mute-302-response-code-from-failure-detection/49186/6 "2024-12-05T10:50:02Z")

</div>

yes, it should.

---

<div class="post-metadata">

**Author:** ![Peter\_Youssef](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/peter_youssef/32/14668_2.png) [@Peter\_Youssef](https://community.dynatrace.com/u/Peter_Youssef)\
**Post date:** [December 7, 2024, 4:03pm UTC](https://community.dynatrace.com/t/mute-302-response-code-from-failure-detection/49186/7 "2024-12-07T16:03:45Z")

</div>

Hi&nbsp;[@suryansh21](https://community.dynatrace.com/user/80497)

PFA helpful resources in addition to the provided guidance by&nbsp;[@erh\_inetum](https://community.dynatrace.com/user/40722)

- [Configure service failure detection in Service Detection v1 — Dynatrace Docs](https://docs.dynatrace.com/docs/observe/applications-and-microservices/services/service-monitoring-settings/configure-service-failure-detection)
- [How to fine tune failure detection](https://www.dynatrace.com/news/blog/how-to-fine-tune-failure-detection/)

Using API V2:

- [Settings API - HTTP failure detection parameters schema table — Dynatrace Docs](https://docs.dynatrace.com/docs/discover-dynatrace/references/dynatrace-api/environment-api/settings/schemas/builtin-failure-detection-service-http-parameters)
- [Failure detection API — Dynatrace Docs](https://docs.dynatrace.com/docs/discover-dynatrace/references/dynatrace-api/configuration-api/service-api/failure-detection)

Hoping it helps.

KR,

Peter

---

<div class="post-metadata">

**Author:** ![kalle\_lahtinen](https://avatars.discourse-cdn.com/v4/letter/k/bb73d2/32.png) [@kalle\_lahtinen](https://community.dynatrace.com/u/kalle_lahtinen)\
**Post date:** [December 7, 2024, 5:39pm UTC](https://community.dynatrace.com/t/mute-302-response-code-from-failure-detection/49186/8 "2024-12-07T17:39:08Z")

</div>

Response code 302 is not considered a failure by default anyway, so there should be no need to separately mute them. If your 302 responses are regarded as failed, maybe you have some uncaught exceptions there which you should ignore in the monitoring instead?

In my opinion the suggested “exclude 302” rule actually does the opposite of muting them, you are saying all 302 responses should be regarded as failed. So the default situation is that 302 is not a failure, but your rule changes that - like it says in the screenshot clearly, “HTTP response codes which indicate an error on the server side” and “HTTP response codes which indicate client side errors”.

---

<div class="post-metadata">

**Author:** ![suryansh21](https://avatars.discourse-cdn.com/v4/letter/s/e95f7d/32.png) [@suryansh21](https://community.dynatrace.com/u/suryansh21)\
**Post date:** [December 9, 2024, 10:33am UTC](https://community.dynatrace.com/t/mute-302-response-code-from-failure-detection/49186/9 "2024-12-09T10:33:43Z")

</div>

Thank you so much

---

<div class="post-metadata">

**Author:** ![suryansh21](https://avatars.discourse-cdn.com/v4/letter/s/e95f7d/32.png) [@suryansh21](https://community.dynatrace.com/u/suryansh21)\
**Post date:** [December 9, 2024, 10:34am UTC](https://community.dynatrace.com/t/mute-302-response-code-from-failure-detection/49186/10 "2024-12-09T10:34:39Z")

</div>

Thank you so much, I got the idea
