I have a few read-only users in PRTG and have configured their accounts with "Allow Acknowledge Alarms" set to "Active". But this does not work, the users cannot acknowledge any alarms.

The only way I could get it to work is to set them as read-write, but I don't want to do that.

These are Active Directory integrated users.

Am I missing something?

Also, could we have the "Allow Acknowledge Alarms" permission at the group level? This way we can create an "acknowledge only" group instead of manually setting the permission on each user account.

Thanks.

Article Comments

Which version are you using? I've tested this out here on a few different versions and haven't been able to reproduce the issue. Is it that the acknowledge alarm menu option isn't there for those users?


Feb, 2014 - Permalink

We recently upgraded to the latest stable version (14.1.8.1308+). However, this seems to be ok now - came back to it after the weekend and the user accounts are fine.

Is there some sort of delay in getting the permissions enabled on accounts (maybe due to session cookies or similar on the user side)? Perhaps I was not patient enough when making these changes on Friday!


Feb, 2014 - Permalink

It can sometimes take 5-10 minutes for the permission changes to take affect so this could have been the issue. Glad that it's working for you now.


Feb, 2014 - Permalink

Thanks - actually, I would like to add another observation which might be related... it seems that read-only users can acknowledge alarms from the list view (which shows all sensors in a certain state), but not from the individual sensor page itself - the only option available there is the "email" icon...

Is this by design?


Feb, 2014 - Permalink

Thanks for the information, I'll look into this and see what I find!


Feb, 2014 - Permalink

I spoke with the developer and he said that this is by design.


Feb, 2014 - Permalink

Ok, thanks.


Feb, 2014 - Permalink

Just to let you know, we are looking into adding this as a result of the feedback. Thanks for the info and hopefully you will see this in the menu soon!


Feb, 2014 - Permalink

That's good news, thanks!

Since we're on this topic, I just noticed what's probably a minor (related) GUI bug that your developers could look into: for a read-only user with "acknowledge alarms" permissions, the drop-down "Acknowledge Alarm(s)" menu gets truncated by the browser.

I suspect this is due to the location of the down arrow being further to the right than when a user has read-write permissions, and everything gets shifted over.

Read-write user, "Acknowledge Alarm(s)" menu: Read-write Users

Read-only user, "Acknowledge Alarm(s)" menu: Read-only Users

The grey bar on the right is my browser's scroll bar. I have tried this in both Chrome and Firefox and the issue is the same in both.

This is not a critical issue as you can still find the appropriate option and click on it, but it does make "aiming" the cursor a bit trickier, since the target area is much smaller and as soon as you go over the browser's scrollbar, it gains focus and the menu disappears.

Thanks again.


Feb, 2014 - Permalink

Thanks for the info! I've made a bug ticket for this problem. It's users like you that help our software get better each day :)


Feb, 2014 - Permalink