Infos:
Used Zammad version: 3.1.x
Used Zammad installation source: rpm
Operating system: ubuntu 18.04
Browser + version: FF latest
Expected behavior:
CheckMK sends mail notifications. eg:
It should close both tickets imho.
Actual behavior:
It just does nothing
I set the group in the integration settings to “Monitoring”, Autoclose on “Yes” and Autoclose Status to “closed”.
Did I missunderstand the function? Did I just made a mistake? Is this a bug?
Maybe a side questions: I see a lot of [prioritized by payment] tags in the GIT Issues. How to do that if I want to support specific requests? I cant find anything about it.
redbear-ger:
I set the group in the integration settings to “Monitoring”, Autoclose on “Yes” and Autoclose Status to “closed”.
Did I missunderstand the function? Did I just made a mistake? Is this a bug
I’m not sure what type the above mentioned monitor is.
If so, you’re affected by this*:
opened 11:07AM - 10 Aug 18 UTC
enhancement
verified
prioritised by payment
<!--
Hi there - thanks for filing an issue. Please ensure the following things … before creating an issue - thank you! 🤓
Since november 15th we handle all requests, except real bugs, at our community board.
Full explanation: https://community.zammad.org/t/major-change-regarding-github-issues-community-board/21
Please post:
- Feature requests
- Development questions
- Technical questions
on the board -> https://community.zammad.org !
If you think you hit a bug, please continue:
- Search existing issues and the CHANGELOG.md for your issue - there might be a solution already
- Make sure to use the latest version of Zammad if possible
- Add the `log/production.log` file from your system. Attention: Make sure no confidential data is in it!
- Please write the issue in english
- Don't remove the template - otherwise we will close the issue without further comments
- Ask questions about Zammad configuration and usage at our mailinglist. See: https://zammad.org/participate
Note: We always do our best. Unfortunately, sometimes there are too many requests and we can't handle everything at once. If you want to prioritize/escalate your issue, you can do so by means of a support contract (see https://zammad.com/pricing#selfhosted).
* The upper textblock will be removed automatically when you submit your issue *
-->
### Infos:
* Used Zammad version: 2.6
* Installation method (source, package, ..): n/a
* Operating system: n/a
* Database + version: n/a
* Elasticsearch version: n/a
* Browser + version: n/a
* Ticket-ID: #1025287
### Expected behavior:
* Service- and Host-Checks should work with Check_MK
### Actual behavior:
* only Service-Checks work
### Steps to reproduce the behavior:
* add check_mk integration
* create a host- and service-check
* only service check will work, as host checks are slightly different
Service-Check:
EventID: $SERVICEPROBLEMID$
Host: XXXXX
Service: $SERVICEDESC$
State: $SERVICESTATE$
Text: $SERVICEOUTPUT$
RemoteIP: 127.0.0.1
UserAgent: curl/7.52.1
Host-Check:
EventID: 19172
Host: swi-1201.sv.nr
Service:
State: DOWN
Text: test
RemoteIP: 127.0.0.1
UserAgent: curl/7.52.1
Service will always be empty.
For Host-Checks there is no $SERVICEPROBLEMID$, but a $HOSTPROBLEMID$
**Edit**
~~Customer asked if it would be possible to be able to also assign a user (customer) to the ticket - this way the ticket wont be from "system".~~ (adressed with Zammad 3.4)
Actually not a bug but -at the moment- out of scope of the integration.
Maybe you’re also having issues with follow ups - that’s what I suspect from “It should close both tickets imho.” (while it should be one, ergo: follow up issue):
opened 10:57AM - 28 Nov 18 UTC
bug
verified
integration
prioritised by payment
<!--
Hi there - thanks for filing an issue. Please ensure the following things … before creating an issue - thank you! 🤓
Since november 15th we handle all requests, except real bugs, at our community board.
Full explanation: https://community.zammad.org/t/major-change-regarding-github-issues-community-board/21
Please post:
- Feature requests
- Development questions
- Technical questions
on the board -> https://community.zammad.org !
If you think you hit a bug, please continue:
- Search existing issues and the CHANGELOG.md for your issue - there might be a solution already
- Make sure to use the latest version of Zammad if possible
- Add the `log/production.log` file from your system. Attention: Make sure no confidential data is in it!
- Please write the issue in english
- Don't remove the template - otherwise we will close the issue without further comments
- Ask questions about Zammad configuration and usage at our mailinglist. See: https://zammad.org/participate
Note: We always do our best. Unfortunately, sometimes there are too many requests and we can't handle everything at once. If you want to prioritize/escalate your issue, you can do so by means of a support contract (see https://zammad.com/pricing#selfhosted).
* The upper textblock will be removed automatically when you submit your issue *
-->
### Infos:
* Used Zammad version: 2.7.x
* Installation method (source, package, ..): 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.
priotized by payment tags and priotizes issues from paying customers. This is one of the perks for having a contract with us.
However, you can -at any time- contact our sales team if you want to priotize a feature or bug even more. Please note that I can’t tell you the costs for this at the moment, but the option is there if needed.
I hope I could light that up a bit
system
February 8, 2020, 11:01am
3
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.
