Support of Tags

[DessaiImrane]

Hi,

I think it could be usefull to support shinken "tags"

So that we can ask for :

• All tags available
• All tags used
• All tags of hosts
• All tags of services ...

I think we can query like that :

• Give me all services group by tag
• Give me all services of the given tag
• Give me all hosts using the given tag
  ...

My guess is that we need :

• a new object "Tag"
• news properties for services and hosts (calleds tags)
• A way to get them from shinken

What do you think ?
Where can I start to look to contribute ?

Thanks

[naparuba]

why not, but livestatus is mainly done for compatibility with the others
tools like thruk or multisite. I think we should also look at adding a real
http layer over the socket so we can export is a the official api, because
core are http but not the data one, seems strange in fact.

for yhe tag, hoss and services already gort them, you only need to declare
them in livestatus mapping I think :)

On Tue, Apr 29, 2014 at 8:02 AM, DessaiImrane [email protected]:

Hi,

I think it could be usefull to support shinken "tags"

So that we can ask for :

• All tags available
• All tags used
• All tags of hosts
• All tags of services ...

I think we can query like that :

• Give me all services group by tag
• Give me all services of the given tag
• Give me all hosts using the given tag ...

My guess is that we need :

• a new object "Tag"
• news properties for services and hosts (calleds tags)
• A way to get them from shinken

What do you think ?
Where can I start to look to contribute ?

Thanks

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

[DessaiImrane]

Indeed, if efforts are already done in Shinken API, no need to go any further with livestatus

I'll let the maintener decides wether to close this issue or not.

Thanks

[naparuba]

I think the overall data backend is really great in livestatus, with hints
and lot of perf tuning from Gerhard, but it's just taht most tools are now
asking for http/json query (we already got json :) ).

so it we can just add a ay to read a GET query, transform it into a LQL
query, get the result and resturn the result into the http socket, we are
good to keep this great module that ask everyone so much efforts :)

On Tue, Apr 29, 2014 at 9:06 AM, DessaiImrane [email protected]:

Indeed, if efforts are already done in Shinken API, no need to go any
further with livestatus

I'll let the maintener decides wether to close this issue or not.

Thanks

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/21#issuecomment-41647053
.

[DessaiImrane]

Ok. Just to be clear I didn't want to offense the main developper, of course ! :)

[naparuba]

nono no problem at all :)

it's just that I think adding http is a thing I'm thinking since months :p

On Tue, Apr 29, 2014 at 9:16 AM, DessaiImrane [email protected]:

Ok. Just to be clear I didn't mean to offense the main developper, of
course ! :)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/21#issuecomment-41647650
.

[vaxvms]

If you don't have anything against php, you can use http://nagios.larsmichelsen.com/livestatusslave/ to serve livestatus over http