[ZBX-18280] Inaccessible user comments to slack Created: 2020 Aug 20  Updated: 2021 Mar 25

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

Type: Incident report Priority: Trivial
Reporter: Chris Voulgaropoulos Assignee: Tikhon Uskov (Inactive)
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Zabbix 5.01


Attachments: PNG File image-2020-08-20-17-49-08-759.png     PNG File image-2020-08-21-09-08-03-161.png     PNG File image-2020-08-21-09-09-39-785.png     PNG File image-2020-08-21-09-11-22-179.png     PNG File image-2020-08-24-11-08-56-932.png    

 Description   

I have a user with permissions to specific host groups, to report to a specific slack channel.

 

 

Steps to reproduce:

  1. Create host groups intended for private tenancy and segregated permission sets of hosts, lets call this tenant A.
  2. Create user with read permissions to tenant A hosts.
  3. Give that user a notification media type to post into Slack channel

 

Result:

The below screenshot shows inaccessible users as the personal who ACK'd the problem.  

It is as though the user with the media associated to the notification, needs elevated privileges to the user listing in order to resolve the name.

 



 Comments   
Comment by Kristians Pavars [ 2020 Aug 20 ]

Hi vtcv

 

Could you please show your Media Type and user configuration?

Can you please show how the action audit looks on Zabbix Frontend (I assume that inaccessible user is resolved there)

 

Thanks,
Kristiāns

 

Comment by Chris Voulgaropoulos [ 2020 Aug 21 ]

 

 

Action Log:

 

The user with the media type is configured as per below: With the hostgroup name blanked out.

 

 

 

 

 

 

Comment by Kristians Pavars [ 2020 Aug 21 ]

Hi vtcv

Can you also please attach message template for this alert? Which macro are you using there?

 

Thanks,
Kristiāns

Comment by Chris Voulgaropoulos [ 2020 Aug 24 ]

Generated at Mon Jun 09 07:46:31 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.