### Author:  [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [April 3, 2025, 7:40pm UTC](https://community.zammad.org/t/checkmk-integration-hostname-and-servicename-in-ticket-title/17237/3 "2025-04-03T19:40:30Z")
With half an eye glimpse looks good to me ™.
Give it a try, restart Zammad and send a test alert and recover it. If shit hits the fan, you can revert within 5 minutes.
Edit:
Look who reported a bug about this… some while… ago
>
>
> \### Infos:
>
> \* Used Zammad version: 2.7.x
> \* Installation method (source, packa…ge, ..): n/a
> \* Operating system: n/a
> \* Database + version: n/a
> \* Elasticsearch version: n/a
> \* Browser + version: n/a
> \* Ticket-ID: #1031272
>
>
> \### Expected behavior:
>
> \* When sending a E-Mail about Service problems regarding the same system, Zammad will append a new article to the same ticket, if the state of the host changes (e.g. State changes back to "OK") or further information are send by check\_mk.
>
> Nagios does work the same way.
>
>
> \### Actual behavior:
>
> \* Zammad opens a new ticket on each E-Mail check\_mk sends, no matter if it's about the same host. It will also not close resolved issue tickets as result of that.
>
>
> \### Steps to reproduce the behavior:
>
> \* Configure check\_mk
> \* change a state of a host to anything other than OK (e.g. Critical) and wait for check\_mk to send the E-Mail
> \* After the E-Mail has been received by Zammad, re check the service state (which will cause a self heal and E-Mail with State "OK")
>
> =\> Zammad will not append the article to the same ticket.
> As this works in Nagios and our Integration page clearly says "\[...\] by API or E-Mail \[...\]" I think this is a bug or should at least get improvement
>
> Yes I'm sure this is a bug and no feature request or a general question.
---
### Author:  [@datenschuft](https://community.zammad.org/u/datenschuft)
#### Post date: [April 4, 2025, 1:06pm UTC](https://community.zammad.org/t/checkmk-integration-hostname-and-servicename-in-ticket-title/17237/4 "2025-04-04T13:06:47Z")
However, the linked issue mentions that CheckMK sends emails and Zammd converts these emails into tickets.
In my case, I’m talking about the Zammad integration checkMK.
CheckMk is talking with zammad via an curl request to an zammad endpoint (URL).
These are probably somewhat different (even though similar) things.
---
### Author:  [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [April 4, 2025, 1:50pm UTC](https://community.zammad.org/t/checkmk-integration-hostname-and-servicename-in-ticket-title/17237/5 "2025-04-04T13:50:18Z")
I wouldn’t wonder if the culprit is the same / a similar one.
But sure, you can create another bug report and mention the old one as possible duplicate. Don’t know.
---
### Author:  [@datenschuft](https://community.zammad.org/u/datenschuft)
#### Post date: [April 18, 2025, 11:40am UTC](https://community.zammad.org/t/checkmk-integration-hostname-and-servicename-in-ticket-title/17237/6 "2025-04-18T11:40:44Z")
It worked for me:
I replaced
title = “#{params[:host]} is #{params[:state]}”
with
title = “#{params[:host]} #{params[:service]} is #{params[:state]}”
---
### Author:  [@system](https://community.zammad.org/u/system)
#### Post date: [April 13, 2026, 11:41am UTC](https://community.zammad.org/t/checkmk-integration-hostname-and-servicename-in-ticket-title/17237/7 "2026-04-13T11:41:03Z")
This topic was automatically closed 360 days after the last reply. New replies are no longer allowed.