[ZBX-17351] Media type messages on acknowledgements show "inaccessible user" Created: 2020 Feb 21  Updated: 2020 Jun 12  Resolved: 2020 Jun 12

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: Andreas Drbal Assignee: Renats Valiahmetovs (Inactive)
Resolution: Won't fix Votes: 0
Labels: Slack, acknowledgements, action, mediatypes
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2020-02-20-16-22-28-880.png     PNG File image-2020-02-20-16-22-38-770.png     PNG File image-2020-04-14-14-24-43-884.png     PNG File image-2020-04-14-14-28-00-043.png    

 Description   

Steps to reproduce:

  1. Configure a Media Type; email or slack. In this case slack was used as an example. Install the zabbix-notify script from the following github project on your Zabbix server - https://github.com/v-zhuravlev/zabbix-notify.
  2. Set up a Zabbix Media Type with the required script parameters.
  3. Set up a Slack webhook to send the data into slack from Zabbix.
  4. When a trigger comes in Acknowledge it.
  5. You will see "Inaccessible user" for the name while the Zabbix UI (Monitoring > Problems) will show who acknowledged it.

Result:
See screenshots. This was also seen in email and not just slack.


Expected: When a user acknowledges the trigger, the media configured should display the user who acknowledged it and not just the UI.

Setup:

  • Zabbix 4.0.15
  • Debian 9 OS
  • PostgreSQL 11.4

Could this be a possible permissions issue?

 Comments   
Comment by Andrei Gushchin (Inactive) [ 2020 Feb 21 ]

Hello Andreas,

What user privileges of the slack user? Do you use impersonal user for common slack notifications?

Comment by Andreas Drbal [ 2020 Feb 21 ]

Hello Andrei,

The user in Zabbix that has the slack media type assigned to it has "Zabbix Admin" privileges and "Read" privileges to the Host Groups that are included in the alerts.

It is indeed an impersonal user for sending common slack notifications.

Let me know if you need any more information.

Thanks & Best Regards,

Andreas

Comment by Andrei Gushchin (Inactive) [ 2020 Feb 26 ]

Gret thank you.
But please let me know what kind of user did acknowledge? What kind of access does it have? What privileges.
I want to understand what that user hasn't access to.

Comment by Andreas Drbal [ 2020 Feb 27 ]

Hello Andrei,

The user that acknowledged it was myself in the frontend. I have super admin privileges on the Zabbix environment.

The process of acknowledging the event starts by selecting the hyperlink from the Slack message:

<https://zabbix.com/zabbix.php?action=acknowledge.edit&eventids[]={EVENT.ID}|Acknowledge>

I'm not sure why this happens from the Action to the UI as a Super Admin user.

Please let me know if you need any more information.

Thanks & Best Regards,

Andreas

Comment by Richie Crews [ 2020 Apr 10 ]

I can confirm the same issue with Zabbix 4.4.7. How do we fix this issue because it would be nice to see via SLACK who acknowledged the alerts. 

Comment by Andreas Drbal [ 2020 Apr 15 ]

Hello,

Based on ZBX-11236 this is intentional by design.

I was able to resolve this by the workaround of creating a User Group and including all users associated with that slack message. Then I tested the Acknowledgement in the UI and was able to see the actual user acknowledging the message in slack.

Thus this ticket can be closed and marked as "Not a bug" as it is indeed not a bug.

here's the outcome in slack

Thanks & Best Regards,

Andreas

Comment by Renats Valiahmetovs (Inactive) [ 2020 Jun 12 ]

Hello!

As it was mentioned earlier in  ZBX-11236 , this does not qualify as a bug, therefore I will be closing this report.

Best Regards,

Generated at Fri Apr 03 15:03:31 EEST 2026 using Jira 10.3.13#10030013-sha1:56dd970ae30ebfeda3a697d25be1f6388b68a422.