'host_notification_period': {
'description': 'The time period in which the contact will be notified about host problems',
'function': lambda item, req: item.host_notification_period.get_name(),
},
And the lambda returns the same (troublesome) object as above.
So it seems that it's not a livestatus bug, but shinken fails to get those periods right from conctact configurations. But just to make sure, I create a issue here.
By the way, currently shinken allows multiple notificationways in one contact configuration. So which one of the host_notification_periods (and other stuffs) do we get?
Hi all, When I tried this:
I got this:
And that couldn't be jsonify:
Here's my configs:
I found these lines in mappings.py
And the lambda returns the same (troublesome) object as above.
So it seems that it's not a livestatus bug, but shinken fails to get those periods right from conctact configurations. But just to make sure, I create a issue here.
By the way, currently shinken allows multiple notificationways in one contact configuration. So which one of the host_notification_periods (and other stuffs) do we get?