Hi all,
I managed to solve this so just thought i'd share the results for other OMD
1.20 users.
To ensure users are created with notifications enabled by default, you need
to configure it in the default user profile.
Unfortunately the default user profile section on wato's "global settings"
will only configure user roles and contact groups, neither of which can
enable the notification option for a user.
You will therefore need to edit the file .etc/check_mk/multisite.d/wato/
global.mk and either add or edit the line "default_user_profile = { ". This
line can include any of the settings found in ./etc/check_mk/config.d/wato/
contacts.mk.
For my setup i added the following to ensure all users were created with
the notification option enabled, and set with with the notification method
"Fleible Custom Notifications"
default_user_profile = {'contactgroups': [], 'notification_method':
('flexible',[{'timeperiod': 'Always'}]),'notifications_enabled': True,
'roles': []}
(I also specified the time period because by default my setup would always
choose one of my custom periods?)
Something to note here as Frank Thilo quite rightly points out in
http://lists.mathias-kettner.de/pipermail/checkmk-en/2013-September/010279.html
"The default user profile is set in etc/check_mk/multisite.d/wato/global.mk.
However, any changes to this file only affect newly created users. If the LDAP
connector already automatically created a user, you'd have to delete the
user and let the connector recreate it."
Therefore after making your changes, just point the ldap user base dn
temporarily to another location to delete the users, then move it back to
recreate the users with the new changes
When I have some more time I intend to further edit my default_user_profile
with another flexible notification rule so that all users are configured to
receive an sms alert for specific hosts/services. Obviously though this
will only succeed for the users in the contact group that have permission
to that host :)
This ability will allow me to overcome my user management issues until OMD
implements a version of check_mk that has the notification rule feature.
Hope this also helps other OMD users,
Cheers!
John
On 2 December 2014 at 09:04, Johnny Duane <[email protected]> wrote:
> Thanks Jaroslaw no problem,
> I suspected it couldn't be done :(
> I have the big decision now on whether we proceed by:
>
> - Managing Individual users manually
> - Upgrade check_mk within OMD 1.20 (which won't be supported should we
> sign up for a support contract)
> - Try OMD's nightly builds (which won't be supported should we sign up
> for a support contract)
>
> Cheers
> John
>
> On 1 December 2014 at 17:00, Jaroslaw Nowak <[email protected]> wrote:
>
>> My fault. I have to apologize, one gets used to handy features much to
>> fast.
>> I am sorry but i actually don't have vanilla 1.20 handy, so i might get
>> it wrong.
>> Set up everything as said b4, after creating contact groups, assign your
>> hosts/services to your contact groups using the rules in the contact group
>> settings.
>> Apologies, my original email was very vague on the details
>> Yes you're absolutely right, We have ldap configured which imports a long
>> list of users and automatically associates them to the appropriate contact
>> groups and permission roles.
>> Unfortunately though all accounts have notifications disabled by default
>> and there is no notifications option in my wato menu. omd 1.20 comes with
>> check_mk 1.2.4p5 which as far as I'm aware does not include the
>> notification rules feature? :(
>>
>> Any further help with enabling notifications for user by default or by
>> certain conditions would be much appreciated
>>
>> Thanks again
>> John
>>
>>
>>
>> Sent from my iPad
>>
>> On 28 Nov 2014, at 17:51, Jaroslaw Nowak <[email protected]> wrote:
>>
>> I'll assume you are using LDAP based authentication. as first you'll like
>> to enable LDAP group sync (users -> LDAP settings -> LDAP group settings).
>> Add users you groups by your needs. Create contact groups named similar to
>> your LDAP groups. Create a new rule (notifications -> new rule) and
>> uncheck notify all, check members of certain group. Choose your condions
>> further down, play with the settings on testgroups to see impact before you
>> roll out.
>> enjoy. ;)
>>
>> W/ regards
>> fate
>> Am 28.11.2014 18:23 schrieb "Johnny Duane" <[email protected]>:
>>
>>> Hi all,
>>>
>>> I'm desperately looking for a method to enable notifications for users
>>> either based on their group/role/permission or just by default?
>>>
>>> I've searched multiple forums for such method, but could only find the
>>> following details:
>>> http://comments.gmane.org/gmane.network.nagios.checkmk/9225
>>>
>>> If this method is still valid, does anyone know what actually needs
>>> adding to global.mk?
>>> If not does anyone know another way?
>>>
>>> I am running OMD 1.20.
>>> (Was gutted that it didn't include check_mks rule based notifications :(
>>> Still rocks though!!!)
>>>
>>> Cheers!
>>> John
>>>
>>> _______________________________________________
>>> omd-users mailing list
>>> [email protected]
>>> http://lists.mathias-kettner.de/mailman/listinfo/omd-users
>>>
>>>
>
_______________________________________________
omd-users mailing list
[email protected]
http://lists.mathias-kettner.de/mailman/listinfo/omd-users
