# Max attempts not reached and hard state

**URL:** <https://community.icinga.com/t/max-attempts-not-reached-and-hard-state/3350>\
**Category:** Icinga 2\
**Created:** [January 29, 2020, 2:46pm UTC](https://community.icinga.com/t/max-attempts-not-reached-and-hard-state/3350 "2020-01-29T14:46:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![GenBuri](https://community.icinga.com/letter_avatar_proxy/v4/letter/g/3bc359/32.png) [@GenBuri](https://community.icinga.com/u/GenBuri)\
**Post date:** [January 29, 2020, 2:46pm UTC](https://community.icinga.com/t/max-attempts-not-reached-and-hard-state/3350/1 "2020-01-29T14:46:29Z")

</div>

Hello !

This is not a problem per se but more an output issue that’s been bugging me.

Every time a service ends up in hard state, the max attempts output next to it doesn’t show, for example, 3/3. It’s always 1/3. Shouldn’t it be 3/3? That’s what we would see in Nagios.

Thank you very much!

---

<div class="post-metadata">

**Author:** ![dnsmichi](https://community.icinga.com/user_avatar/community.icinga.com/dnsmichi/32/7721_2.png) [@dnsmichi](https://community.icinga.com/u/dnsmichi)\
**Post date:** [January 29, 2020, 3:04pm UTC](https://community.icinga.com/t/max-attempts-not-reached-and-hard-state/3350/2 "2020-01-29T15:04:53Z")

</div>

Hi,

the state attempt counting is only important for SOFT states. This measures the attempts til a HARD state change occurs firing notifications. When a service continues being checked, and is still NOT-OK, this counter is not incremented anymore. Thus leading to false information, that is why it is hidden in Icinga Web for HARD states.

Cheers,  
Michael

---

<div class="post-metadata">

**Author:** ![GenBuri](https://community.icinga.com/letter_avatar_proxy/v4/letter/g/3bc359/32.png) [@GenBuri](https://community.icinga.com/u/GenBuri)\
**Post date:** [January 29, 2020, 3:33pm UTC](https://community.icinga.com/t/max-attempts-not-reached-and-hard-state/3350/3 "2020-01-29T15:33:46Z")

</div>

Ok I get it. Thank you @dnsmichi
