Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Livestatus fields (MK v1.2.1) #15

Open
obinand opened this issue Mar 12, 2014 · 15 comments
Open

New Livestatus fields (MK v1.2.1) #15

obinand opened this issue Mar 12, 2014 · 15 comments

Comments

@obinand
Copy link

obinand commented Mar 12, 2014

Hello,

When do you plan to track changes to MK_Livestatus, at the statehist (v1.2.1) and the host_staleness and service_staleness field? To be compatible with check_mk as frontend

Olivier

@naparuba
Copy link
Member

what are theses fields values? :)

thanks,

Jean

On Wed, Mar 12, 2014 at 10:48 PM, obinand [email protected] wrote:

Hello,

When do you plan to track changes to MK_Livestatus, at the statehist
(v1.2.1) and the host_staleness and service_staleness field? To be
compatible with check_mk as frontend

Olivier

Reply to this email directly or view it on GitHubhttps://github.com//issues/15
.

@obinand
Copy link
Author

obinand commented Mar 13, 2014

statehist is a table like this with host-level description check_mk
statehist - sla statistics for hosts and services, joined with data from hosts, services and log.

For the other fields I do not know what they are, I will mount a check_mk dedicated server to identify the values ​​of these fields

Olivier

@naparuba
Copy link
Member

We wil need some dumps to see what is exactly in there because here I don't
understand :p

On Thu, Mar 13, 2014 at 9:53 AM, obinand [email protected] wrote:

statehist is a table like this with host-level description check_mk
statehist - sla statistics for hosts and services, joined with data from
hosts, services and log.

For the other fields I do not know what they are, I will mount a check_mk
dedicated server to identify the values of these fields

Olivier

Reply to this email directly or view it on GitHubhttps://github.com//issues/15#issuecomment-37511053
.

@Frescha
Copy link
Contributor

Frescha commented Mar 15, 2014

New helpful title ...

@olivierHa olivierHa added the bug label Nov 10, 2014
@olivierHa
Copy link
Member

Hello, I've updated this issue.
I think this post is also related to this issue.
http://www.shinken-monitoring.org/forum/index.php?topic=1858.0

It appears that recent version of MK_Multisite is no more usable with our livestatus module :(

@olivierHa
Copy link
Member

In fact : https://mathias-kettner.de/check_mk_changelog_stable.html

New in version 1.2.3i2:

Livestatus

new service column staleness: indicator for outdated service checks
new host column staleness: indicator for outdated host checks

MultiSite :

"Unchecked Services" view now uses the staleness of services for filtering

@jm42
Copy link

jm42 commented Dec 20, 2014

+1

1 similar comment
@ghost
Copy link

ghost commented Jan 8, 2015

+1

@Corbyn
Copy link

Corbyn commented Jun 26, 2015

Hi,

what's the current status of Shinken Livestatus regarding "statehist" table and "staleness" columns?
We desperately need these features for reporting and NagVis... :)

Andy

@X-dark
Copy link

X-dark commented Nov 30, 2015

Is there at least a workaround like returning hardcoded value?

@X-dark
Copy link

X-dark commented Nov 30, 2015

Answering myself. Here is a quick workaround to return a hardcoded value for staleness (needed by Nagvis):

--- var/lib/shinken/modules/livestatus/mapping.py.orig  2015-11-30 15:16:42.829682487 +0100
+++ var/lib/shinken/modules/livestatus/mapping.py       2015-11-30 15:38:01.415712971 +0100
@@ -682,6 +682,10 @@
             'function': lambda item, req: [get_livestatus_full_name(i, req) for i in item.source_problems],  # REPAIRME MAYBE (separators in python and csv)
             'datatype': list,
         },
+        'staleness': {
+            'description': 'FIXME',
+            'function': lambda item, req: 0,
+        },
         'state': {
             'description': 'The current state of the host (0: up, 1: down, 2: unreachable)',
             'function': lambda item, req: item.state_id,
@@ -1466,6 +1470,10 @@
             'function': lambda item, req: "",  # REPAIRME
             'datatype': list,
         },
+        'staleness': {
+            'description': 'FIXME',
+            'function': lambda item, req: 0,
+        },
         'state': {
             'description': 'The current state of the service (0: OK, 1: WARN, 2: CRITICAL, 3: UNKNOWN)',
             'function': lambda item, req: item.state_id,

@fpeterschmitt
Copy link

This patch works perfectly with Shinken 2.4.2, thanks ;-)

Also, nagvis was complaining about not finding servicegroups. At first sight, the problem isn't related to this… but it is related to.

@olivierHa
Copy link
Member

@X-dark , could you make a PR with your quick patch ?
Do you want me to do it ?

@X-dark
Copy link

X-dark commented Mar 4, 2016

@olivierHa I can but would it not be better to implement this new field properly?

@olivierHa
Copy link
Member

Yes,of course it would be better.
But on my side, I got no time for this right now, and people are stuck with
this issue right now.

At least, nagvis will work ...

2016-03-04 15:08 GMT+01:00 Cedric Girard [email protected]:

@olivierHa https://github.com/olivierHa I can but would it not be
better to implement this new field properly?


Reply to this email directly or view it on GitHub
#15 (comment)
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants