shinken-devel — Devel list for the Shinken project

Re: [Shinken-devel] How to do a reload in Shinken

[nap <nap...@gm...>]

On Thu, Apr 23, 2015 at 6:12 AM, Andy Xie <and...@gm...> wrote:

> Recently, our team want to make use Shinken to monitor our services.
>
> In our situation, we need to modify the configuration a little bit more.
> Every time the configuration change we should user the reload function
> provided by the Shinken init.d script which  will turn out to stop arbiter
> and start it again. a little bit more on reload of Shinken with this will
> make arbiter unavailable for some time.
>
> However, if we do not reload the configuration as soon as the
> configuration changes we can lose some thing if the service is not OK. So,
> what schema will mostly you chose to do a reload and what make you choose
> that schema. :)
>
Hi,

There is no perfect solution currently for this. One problem is that the
current init.d script is not using the best solution for the arbiter case.
When you reload, one big part of the time is used to read the
configuration, parse/create/link objects, and finally serialize them (that
part is maybe the biggest one).

But all of this do not need the old arbiter to be killed (you can have the
old one still running and the new working and consumming the CPU for the
serialization).

We should change the reload call to not stop the old arbiter, but instead
call the new arbiter with the -r option: when going to daemon (so after the
load phase if I'm not wrong) that's the new arbiter that will kill the old
one. So it will be killed "only when need" ^^

You can give a try by hand (-d and -r so for your new arbiter) and see the
effect on the "arbiter off" duration ^^



Jean



>
> ++++++
> Ning Xie
>

[Shinken-devel] How to do a reload in Shinken

[Andy X. <and...@gm...>]

Recently, our team want to make use Shinken to monitor our services.

In our situation, we need to modify the configuration a little bit more.
Every time the configuration change we should user the reload function
provided by the Shinken init.d script which  will turn out to stop arbiter
and start it again. a little bit more on reload of Shinken with this will
make arbiter unavailable for some time.

However, if we do not reload the configuration as soon as the configuration
changes we can lose some thing if the service is not OK. So, what schema
will mostly you chose to do a reload and what make you choose that schema.
:)



++++++
Ning Xie

[Shinken-devel] Broker memory blowout

[David G. <dg...@wi...>]

We have a Shinken installation using version 2.2.  We have 5 servers. 
Each server has 40 CPU cores and 64GB of RAM.  One server (shinken1) is 
running all of the daemons (arbiter, broker, scheduler, poller, 
receiver, reactionner).  Three servers (shinken2, shinken3, shinken4) 
run only a scheduler and poller.  The last server (shinken5) is a spare 
for all daemons.

Our current configuration (which is still being setup) has 2118 hosts 
and 19374 services and everything is running smoothly except that the 
Thruk interface seems a bit sluggish.

However, when I change the normal_check_interval from 5 to 1 and the 
retry_check_interval from 2 to 1 (to match the current Nagios 
implementation) we start to have problems.  The broker daemon starts to 
use more and more memory and CPU and then I start to see a lot of 
timeouts and configuration reassignments in the arbiter log.  I've seen 
a broker process get up to 30GB of memory and 120% CPU at which point 
Shinken is pretty much unusable.

Any idea what would cause this?  Is it just that I need more capacity to 
run the extra checks?  Would adding another poller and scheduler to 
shinken2-4 help?  They seem to have plenty of CPU and RAM to spare still.

Re: [Shinken-devel] Shinken 2.4 RC1 is out!

[Hermann L. <Her...@iw...>]

Hello All,

On Mon, Apr 13, 2015 at 12:27:17PM -0400, Sebastien Coavoux wrote:
> >> >>    - Also, I think we don't use setuptools as we should. If you look at
> >> >>    what ansible/salt do, they don't ship any files outside /usr/local/ folder
> >> >>    (using ie: sudo pip install salt). I didn't find any python software which
> >> >>    copy configuration files in /etc/ or makes some chown during the
> >> >>    installation (pip install ...).
> > 
> > That are exactely the issues I saw also while trying to debianize 
> > shinken
> > in the past. With a well written setup.py you can:
> >  - install in your home directory
> >  - run "python setup.py --command-packages=stdeb.command debianize" to
> >  build a .deb at any time.
> > 
> That was the whole purpose of the setup rework : to have a "well 
> written" file :)

The high art of packaging is to allow packaging as non root:
> dpkg-buildpackage -b -rfakeroot
produces a nice python-shinken_2.4-rc2-1_all.deb on jessie, which I have to test now.

Big thanks for that progress, guys!

> > Not familiar to this, but read about a month ago (from a french guy 
> > btw):
> > Did the wheel format bring any improvement in this area ?
> > 
> As far as I known wheel is for caching purpose.

Sorry, don't intended to make advertisement for Julien Danjou: The Hacker's guide
to Python, where chapter4 is about python packaging and distribution and that PEP 427
was written to define a new python packaging standard: wheel.

> I really think there is communication problem there. Issues are not 
> clearly stated and there is no real direction to fix them. I mean, there 
> was no clear communication saying : "Ok we are reverting on this day if 
> no fix is found and release on this (other) day. We want the setup.py to 
> be consistent balbla". Is this being too "pro" to do so?
> People that don't check what's going on Github won't know that we 
> reverted that today, too bad for them.
> 
> 
> I'm raising all this here because it's devel list, maybe we should 
> create users list because people may not be interested in this debate.

As an old fashioned guy with unfortunately little time (new building has to
be finished this year) I like the dev list to hear about your progress,
and also +1 for a users list.

Thanks,
 greetings
   Hermann

-- 
Netzwerkadministration/Zentrale Dienste, Interdiziplinaeres 
Zentrum fuer wissenschaftliches Rechnen der Universitaet Heidelberg
IWR; INF 368; 69120 Heidelberg; Tel: (06221)54-8236 Fax: -5224
Email: Her...@iw...

Re: [Shinken-devel] Shinken 2.4 RC1 is out!

[Sebastien C. <s.c...@fr...>]

Hi everyone,

(Back from holidays too)

Le 2015-04-13 05:11, Hermann Lauer a écrit :
> Hello All,
> 
> On Wed, Apr 08, 2015 at 09:51:07AM +0800, Andy Xie wrote:
>> currently, there are some docker container in dockerhub. Here is the 
>> url:
>> https://registry.hub.docker.com/search?q=shinken
> 
> nice to know, thanks.
> 
>> > still issue on debian (I didn't test centos). But the Travis part is ok.
>> >
>> >> But I have two comments about all of this:
>> >>
>> >>    - BETA tags seem to be useless, otherwise someone would have reported
>> >>    this bug earlier...
>> >>
>> >>  Sad but true. don't expect people to test a beta (unless they are core
>> > dev). Even the test level is quite low on RC. It's mainly on few days after
>> > the release that we have the most bug ticket.
>> >
Well, to be honest I don't think (all) core devs tried it. I personally 
gave a try focusing on BSD part (to not bother ddurieux everytime)
and the new feature added (develop). Unless you try the virtualenv part 
only, I doubt you did try the beta tag Nap.
My solution to that is barely the one I give every time : add some 
automation and testing. If we are lazy to test then code something to 
make it for us (sysadmin default behavior). But nothing will replace 
peer reviewing.

>> >>
>> >>    - Also, I think we don't use setuptools as we should. If you look at
>> >>    what ansible/salt do, they don't ship any files outside /usr/local/ folder
>> >>    (using ie: sudo pip install salt). I didn't find any python software which
>> >>    copy configuration files in /etc/ or makes some chown during the
>> >>    installation (pip install ...).
> 
> That are exactely the issues I saw also while trying to debianize 
> shinken
> in the past. With a well written setup.py you can:
>  - install in your home directory
>  - run "python setup.py --command-packages=stdeb.command debianize" to
>  build a .deb at any time.
> 
That was the whole purpose of the setup rework : to have a "well 
written" file :)

>> >>    I feel like pip is made to install libs more than full software
>> >>
>> >> Yes, the whole python ecosystem was done for libs, not tools :(
Then why stick with non standard / dirty / custom setup files? After 
all, I think the install script is not that stupid.
What we defined previously as a "normal" install is not really normal in 
the python world. Maybe we should just call a "clean" setup.py from a 
shell script to make this "normal" install. I bet it's only a matter of 
3 lines in shell (adduser, chown, python setup.py --magical-paramaters).
Of course, this prevent from doing a "normal" install from pip, but I 
don't think we are using it the good way.
It's something to really think about because it simplify a lot the 
maintaining. This first step done, nightly packaging should be a piece 
of cake.

> 
> Not familiar to this, but read about a month ago (from a french guy 
> btw):
> Did the wheel format bring any improvement in this area ?
> 
As far as I known wheel is for caching purpose.

>> > In the next years, I think docker-like ship will be the default (think
>> > about docker-like plugins! no more system/python/perl lib issue ^^), and
>> > users won't even have to mix local system and applications. And they won't
>> > even care where it's installed in the container (as it's a black box and it
>> > won't break their system).
> 
> Not so shure about this - you need still a good base distribution
> maintained by trustfull
> people with long term support.
> 
Well, for now docker has still work to do IMO. It's a new "in" 
technology but it need some improvements (last time I tried with fedora 
was a failure).
I don't think we can wait for docker to be "cool" enough to provide the 
community "proper" install methods.

>> > All we need for this are (easier) orchestration tools and more powerful
> 
> Better system administration tools - salt is an improvement in this 
> area,
> but there is much room left in this area. But that will need time, so 
> this is
> relying on to be written software...
> 
>> > container monitoring (currently it's not so natural to monitor containers
>> > as they can spawn quickly).
> 
> New tasks for shinken ;-)
> 
>> > It can be docker or another container solution, but as it can save a lot
>> > of time to admins to install/link new tools, I think it will be really
>> > asked in production, and not just a dev playground tool ^^
> 
> That is also my feeling, while the classical distribution systems will 
> be used
> also - at least during the next years. One plus I see there is also the 
> keeping
> of record of configuration of packages you installed in the past in a 
> cheap way.
> 

I would like to come back on the way this release is handled. This is 
the devel list but we all now that some users are on it. This is our 
main way to keep them updated on what is happening now. Unfortunately I 
cannot see any info about what is going to happen to the release on this 
list. I try my best on the previous email to explain why the release was 
late and what were the next steps but nothing more since.
Am I the only one to care about being consistent with what we've 
announced before? The release is 13 days late, I think people deserve 
some news. IRC is a place to share but there are not as many people on 
that medium.
I really think there is communication problem there. Issues are not 
clearly stated and there is no real direction to fix them. I mean, there 
was no clear communication saying : "Ok we are reverting on this day if 
no fix is found and release on this (other) day. We want the setup.py to 
be consistent balbla". Is this being too "pro" to do so?
People that don't check what's going on Github won't know that we 
reverted that today, too bad for them.


I'm raising all this here because it's devel list, maybe we should 
create users list because people may not be interested in this debate.


Regards,


Sébastien

> But just my 2pence after Easter holidays,
> thanks for your work and
>  greetings
>    Hermann
> 
> --
> Netzwerkadministration/Zentrale Dienste, Interdiziplinaeres
> Zentrum fuer wissenschaftliches Rechnen der Universitaet Heidelberg
> IWR; INF 368; 69120 Heidelberg; Tel: (06221)54-8236 Fax: -5224
> Email: Her...@iw...
> 
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live 
> exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- 
> event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> Shinken-devel mailing list
> Shi...@li...
> https://lists.sourceforge.net/lists/listinfo/shinken-devel

Re: [Shinken-devel] Shinken 2.4 RC1 is out!

[Hermann L. <Her...@iw...>]

Hello All,

On Wed, Apr 08, 2015 at 09:51:07AM +0800, Andy Xie wrote:
> currently, there are some docker container in dockerhub. Here is the url:
> https://registry.hub.docker.com/search?q=shinken

nice to know, thanks.

> > still issue on debian (I didn't test centos). But the Travis part is ok.
> >
> >> But I have two comments about all of this:
> >>
> >>    - BETA tags seem to be useless, otherwise someone would have reported
> >>    this bug earlier...
> >>
> >>  Sad but true. don't expect people to test a beta (unless they are core
> > dev). Even the test level is quite low on RC. It's mainly on few days after
> > the release that we have the most bug ticket.
> >
> >>
> >>    - Also, I think we don't use setuptools as we should. If you look at
> >>    what ansible/salt do, they don't ship any files outside /usr/local/ folder
> >>    (using ie: sudo pip install salt). I didn't find any python software which
> >>    copy configuration files in /etc/ or makes some chown during the
> >>    installation (pip install ...).

That are exactely the issues I saw also while trying to debianize shinken
in the past. With a well written setup.py you can:
 - install in your home directory
 - run "python setup.py --command-packages=stdeb.command debianize" to
 build a .deb at any time.

> >>    I feel like pip is made to install libs more than full software
> >>
> >> Yes, the whole python ecosystem was done for libs, not tools :(

Not familiar to this, but read about a month ago (from a french guy btw):
Did the wheel format bring any improvement in this area ?

> > In the next years, I think docker-like ship will be the default (think
> > about docker-like plugins! no more system/python/perl lib issue ^^), and
> > users won't even have to mix local system and applications. And they won't
> > even care where it's installed in the container (as it's a black box and it
> > won't break their system).

Not so shure about this - you need still a good base distribution maintained by trustfull
people with long term support.

> > All we need for this are (easier) orchestration tools and more powerful

Better system administration tools - salt is an improvement in this area,
but there is much room left in this area. But that will need time, so this is
relying on to be written software...

> > container monitoring (currently it's not so natural to monitor containers
> > as they can spawn quickly).

New tasks for shinken ;-)

> > It can be docker or another container solution, but as it can save a lot
> > of time to admins to install/link new tools, I think it will be really
> > asked in production, and not just a dev playground tool ^^

That is also my feeling, while the classical distribution systems will be used
also - at least during the next years. One plus I see there is also the keeping
of record of configuration of packages you installed in the past in a cheap way.

But just my 2pence after Easter holidays,
thanks for your work and
 greetings
   Hermann

-- 
Netzwerkadministration/Zentrale Dienste, Interdiziplinaeres 
Zentrum fuer wissenschaftliches Rechnen der Universitaet Heidelberg
IWR; INF 368; 69120 Heidelberg; Tel: (06221)54-8236 Fax: -5224
Email: Her...@iw...

Re: [Shinken-devel] Shinken 2.4 RC1 is out!

[Andy X. <and...@gm...>]

currently, there are some docker container in dockerhub. Here is the url:
https://registry.hub.docker.com/search?q=shinken



++++++
Ning Xie


2015-04-07 21:59 GMT+08:00 nap <nap...@gm...>:

>
>
> On Thu, Apr 2, 2015 at 10:51 PM, Thibault Cohen <tit...@gm...>
> wrote:
>
>>  Hello everyone !
>>
>> I'm guilty, this is my fault... :( sorry.
>>
>> I just created a new pull request that should fix this bug :)
>>
> Hi,
>
> still issue on debian (I didn't test centos). But the Travis part is ok.
>
>> But I have two comments about all of this:
>>
>>    - BETA tags seem to be useless, otherwise someone would have reported
>>    this bug earlier...
>>
>>  Sad but true. don't expect people to test a beta (unless they are core
> dev). Even the test level is quite low on RC. It's mainly on few days after
> the release that we have the most bug ticket.
>
>>
>>    - Also, I think we don't use setuptools as we should. If you look at
>>    what ansible/salt do, they don't ship any files outside /usr/local/ folder
>>    (using ie: sudo pip install salt). I didn't find any python software which
>>    copy configuration files in /etc/ or makes some chown during the
>>    installation (pip install ...).
>>    I feel like pip is made to install libs more than full software
>>
>> Yes, the whole python ecosystem was done for libs, not tools :(
>
>
>>    - Maybe we need to rethink about what setup.py should do and should
>>    not do...
>>
>> For linux installation, I think we should get inspiration from BSD folder
>> architecture generated by pip installation.
>>
> We already finish this talk on the pre-2.0 version and we did choose the
> LSB. We won't change again as it's a valid way to find files after all.
>
> In the next years, I think docker-like ship will be the default (think
> about docker-like plugins! no more system/python/perl lib issue ^^), and
> users won't even have to mix local system and applications. And they won't
> even care where it's installed in the container (as it's a black box and it
> won't break their system).
>
> All we need for this are (easier) orchestration tools and more powerful
> container monitoring (currently it's not so natural to monitor containers
> as they can spawn quickly).
>
> It can be docker or another container solution, but as it can save a lot
> of time to admins to install/link new tools, I think it will be really
> asked in production, and not just a dev playground tool ^^
>
>  [...]
>>
>> --
>> Thibault Cohen
>>
>>
>
> Jean
>
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live
> exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
> event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> Shinken-devel mailing list
> Shi...@li...
> https://lists.sourceforge.net/lists/listinfo/shinken-devel
>
>

Re: [Shinken-devel] Shinken 2.4 RC1 is out!

[nap <nap...@gm...>]

On Thu, Apr 2, 2015 at 10:51 PM, Thibault Cohen <tit...@gm...>
wrote:

>  Hello everyone !
>
> I'm guilty, this is my fault... :( sorry.
>
> I just created a new pull request that should fix this bug :)
>
Hi,

still issue on debian (I didn't test centos). But the Travis part is ok.

> But I have two comments about all of this:
>
>    - BETA tags seem to be useless, otherwise someone would have reported
>    this bug earlier...
>
>  Sad but true. don't expect people to test a beta (unless they are core
dev). Even the test level is quite low on RC. It's mainly on few days after
the release that we have the most bug ticket.

>
>    - Also, I think we don't use setuptools as we should. If you look at
>    what ansible/salt do, they don't ship any files outside /usr/local/ folder
>    (using ie: sudo pip install salt). I didn't find any python software which
>    copy configuration files in /etc/ or makes some chown during the
>    installation (pip install ...).
>    I feel like pip is made to install libs more than full software
>
> Yes, the whole python ecosystem was done for libs, not tools :(


>    - Maybe we need to rethink about what setup.py should do and should
>    not do...
>
> For linux installation, I think we should get inspiration from BSD folder
> architecture generated by pip installation.
>
We already finish this talk on the pre-2.0 version and we did choose the
LSB. We won't change again as it's a valid way to find files after all.

In the next years, I think docker-like ship will be the default (think
about docker-like plugins! no more system/python/perl lib issue ^^), and
users won't even have to mix local system and applications. And they won't
even care where it's installed in the container (as it's a black box and it
won't break their system).

All we need for this are (easier) orchestration tools and more powerful
container monitoring (currently it's not so natural to monitor containers
as they can spawn quickly).

It can be docker or another container solution, but as it can save a lot of
time to admins to install/link new tools, I think it will be really asked
in production, and not just a dev playground tool ^^

 [...]
>
> --
> Thibault Cohen
>
>

Jean

Re: [Shinken-devel] Configure Shinken remotely

[David G. <dav...@gm...>]

using thruk work prety well to. All you have to do is to install
mod-livestatus and configure shinken backend in thruk (keep in mind that
thruk must run on the server where arbiter daemon run).



2015-03-26 15:24 GMT+01:00 Felipe Zanchet Grazziotin <fe...@st...>:

> I am using Shinken config with Adagios and it works nicely. No patching
> needed, just set the configuration accordingly.
>
> http://www.adagios.org/
>
> Regards
>
>
>
>
> On 26 March 2015 at 14:00, Smain Kahlouch <sma...@gm...> wrote:
>
>> Hi everyone,
>>
>> I would like to know if there's a way of creating/changing shinken's
>> configuration remotely please ?
>> I was thinking about a kind of restfull api or something similar.
>>
>> Thank you,
>> Smana
>>
>>
>> ------------------------------------------------------------------------------
>> Dive into the World of Parallel Programming The Go Parallel Website,
>> sponsored
>> by Intel and developed in partnership with Slashdot Media, is your hub
>> for all
>> things parallel software development, from weekly thought leadership
>> blogs to
>> news, videos, case studies, tutorials and more. Take a look and join the
>> conversation now. http://goparallel.sourceforge.net/
>> _______________________________________________
>> Shinken-devel mailing list
>> Shi...@li...
>> https://lists.sourceforge.net/lists/listinfo/shinken-devel
>>
>>
>
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live
> exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
> event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> Shinken-devel mailing list
> Shi...@li...
> https://lists.sourceforge.net/lists/listinfo/shinken-devel
>
>

Re: [Shinken-devel] Shinken 2.4 RC1 is out!

[Thibault C. <tit...@gm...>]

 

Hello everyone ! 

I'm guilty, this is my fault... :( sorry. 

I
just created a new pull request that should fix this bug :) 

But I have
two comments about all of this: 

 	* BETA tags seem to be useless,
otherwise someone would have reported this bug earlier...

	* Also, I
think we don't use setuptools as we should. If you look at what
ansible/salt do, they don't ship any files outside /usr/local/ folder
(using ie: sudo pip install salt). I didn't find any python software
which copy configuration files in /etc/ or makes some chown during the
installation (pip install ...).
I feel like pip is made to install libs
more than full software
Maybe we need to rethink about what setup.py
should do and should not do... 

For linux installation, I think we
should get inspiration from BSD folder architecture generated by pip
installation. 

You can try with (while the PR is not merged): 

 	*
Debian/Ubuntu

 	* pip install
https://github.com/titilambert/shinken/archive/sudo_setup_py.zip [3]
--install-option="--install-layout=deb"

 	* CentOS

 	* pip install
https://github.com/titilambert/shinken/archive/sudo_setup_py.zip [3]


	* BSD

 	* 
 	* pip install
https://github.com/titilambert/shinken/archive/sudo_setup_py.zip
[3]

Don't forget to create shinken user on your shinken ;) 

Have nice
tests 

-- 
Thibault Cohen

Le 02/04/2015 04:19, nap a écrit : 

> Hi,

> 
> On Wed, Apr 1, 2015 at 3:55 AM, Sebastien Coavoux
<s.c...@fr...> wrote:
> 
>> Hi there!
>> 
>> We are a bit late on
schedule, the 2.4 should have been tagged today but
>> as we did not
made a prior notice for a RC we choose to only tag a RC.
>> [...]
> 
>
we did find a regression on debian&centos on the default setup.py
behavior (install on /usr/local/etc/shinken instead of /etc/shinken), so
we will fix this and release a RC2 as soon as it's ok :) 
> 
> Jean 
>

>
------------------------------------------------------------------------------
>
Dive into the World of Parallel Programming The Go Parallel Website,
sponsored
> by Intel and developed in partnership with Slashdot Media,
is your hub for all
> things parallel software development, from weekly
thought leadership blogs to
> news, videos, case studies, tutorials and
more. Take a look and join the 
> conversation now.
http://goparallel.sourceforge.net/ [1]
> 
>
_______________________________________________
> Shinken-devel mailing
list
> Shi...@li...
>
https://lists.sourceforge.net/lists/listinfo/shinken-devel [2]



Links:
------
[1] http://goparallel.sourceforge.net/
[2]
https://lists.sourceforge.net/lists/listinfo/shinken-devel
[3]
https://github.com/titilambert/shinken/archive/sudo_setup_py.zip

Re: [Shinken-devel] Shinken 2.4 RC1 is out!

[nap <nap...@gm...>]

Hi,



On Wed, Apr 1, 2015 at 3:55 AM, Sebastien Coavoux <s.c...@fr...> wrote:

> Hi there!
>
> We are a bit late on schedule, the 2.4 should have been tagged today but
> as we did not made a prior notice for a RC we choose to only tag a RC.
> [...]
>
> we did find a regression on debian&centos on the default setup.py behavior
(install on /usr/local/etc/shinken instead of /etc/shinken), so we will fix
this and release a RC2 as soon as it's ok :)


Jean

[Shinken-devel] Shinken 2.4 RC1 is out!

[Sebastien C. <s.c...@fr...>]

Hi there!

We are a bit late on schedule, the 2.4 should have been tagged today but 
as we did not made a prior notice for a RC we choose to only tag a RC.
We need some tests and feedback before pushing the real 2.4 because we 
still have nothing magic to run a feature-complete test :) (we are 
thinking a lot about how to start that).
You can install this tag with a simple pip install 
https://github.com/naparuba/shinken/archive/2.4-RC1.zip. Pip will do the 
job for you!
The release note are here : 
https://github.com/naparuba/shinken/blob/master/Changelog. It is mainly 
bug fixing and code stabilization.
However I would like to highlight to of them :
* Pep8 : Shinken is now pep8 compliant (only 3 rules a ignored), and 
Travis enforces pep8 for new code.
* Setup.py : if you are used to python virtualenv, you will be happy 
with this release. The setup script has been rewritten with pbr and 
allow to install Shinken in a virtualenv. You also have the possibility 
to install Shinken as a lib (python setup.py develop) so that you don't 
have sample config files provided.

We would like to tag the final 2.4 by the end of the week so that we 
don't drift too much from the schedule, but of course quality is more 
important that strict schedule. Next time we will tag this one or two 
week before the official release date.

Have fun trying Shinken 2.4!

Sébastien Coavoux

Re: [Shinken-devel] Configure Shinken remotely

[Smain K. <sma...@gm...>]

Thanks Felipe :)  i'll have a look at it.

Regards,
Smana

2015-03-26 15:25 GMT+01:00 Felipe openglx <op...@st...>:

> I am using Shinken config with Adagios and it works nicely. No patching
> needed, just set the configuration accordingly.
>
> http://www.adagios.org/
>
> Regards
>
> PS: moderator I've replied with another e-mail address before, my apologies
>
> On 26 March 2015 at 14:00, Smain Kahlouch <sma...@gm...> wrote:
>
>> Hi everyone,
>>
>> I would like to know if there's a way of creating/changing shinken's
>> configuration remotely please ?
>> I was thinking about a kind of restfull api or something similar.
>>
>> Thank you,
>> Smana
>>
>>
>> ------------------------------------------------------------------------------
>> Dive into the World of Parallel Programming The Go Parallel Website,
>> sponsored
>> by Intel and developed in partnership with Slashdot Media, is your hub
>> for all
>> things parallel software development, from weekly thought leadership
>> blogs to
>> news, videos, case studies, tutorials and more. Take a look and join the
>> conversation now. http://goparallel.sourceforge.net/
>> _______________________________________________
>> Shinken-devel mailing list
>> Shi...@li...
>> https://lists.sourceforge.net/lists/listinfo/shinken-devel
>>
>>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Shinken-devel mailing list
> Shi...@li...
> https://lists.sourceforge.net/lists/listinfo/shinken-devel
>
>

Re: [Shinken-devel] Configure Shinken remotely

[Felipe o. <openglx@StarByte.net>]

I am using Shinken config with Adagios and it works nicely. No patching
needed, just set the configuration accordingly.

http://www.adagios.org/

Regards

PS: moderator I've replied with another e-mail address before, my apologies

On 26 March 2015 at 14:00, Smain Kahlouch <sma...@gm...> wrote:

> Hi everyone,
>
> I would like to know if there's a way of creating/changing shinken's
> configuration remotely please ?
> I was thinking about a kind of restfull api or something similar.
>
> Thank you,
> Smana
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Shinken-devel mailing list
> Shi...@li...
> https://lists.sourceforge.net/lists/listinfo/shinken-devel
>
>

Re: [Shinken-devel] Configure Shinken remotely

[Felipe Z. G. <fe...@st...>]

I am using Shinken config with Adagios and it works nicely. No patching
needed, just set the configuration accordingly.

http://www.adagios.org/

Regards




On 26 March 2015 at 14:00, Smain Kahlouch <sma...@gm...> wrote:

> Hi everyone,
>
> I would like to know if there's a way of creating/changing shinken's
> configuration remotely please ?
> I was thinking about a kind of restfull api or something similar.
>
> Thank you,
> Smana
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Shinken-devel mailing list
> Shi...@li...
> https://lists.sourceforge.net/lists/listinfo/shinken-devel
>
>

[Shinken-devel] Configure Shinken remotely

[Smain K. <sma...@gm...>]

Hi everyone,

I would like to know if there's a way of creating/changing shinken's
configuration remotely please ?
I was thinking about a kind of restfull api or something similar.

Thank you,
Smana

Re: [Shinken-devel] Current work on Livestatus & monitoring checks survey ^^

[Hermann L. <Her...@iw...>]

Hello All,

On Wed, Mar 11, 2015 at 09:50:10PM +0100, nap wrote:
> On Wed, Mar 11, 2015 at 3:38 PM, Sven Nierlein <sv...@ni...> wrote:
> 
> > Hi Jean,
> >
> > I am missing an answer for the "What if such "lower" importance checks can
> > be hidden by default on the "services" view?"
> >
> >  - i am using this in thruk already[1]

just to get informed (had very little time) - is there any plan
for a more pythonic interface to the configuration in the meantime ?

Just dreaming about changing the configuration on the fly due to manipulating
unimportant services away or changing notifications or adding/removing hosts
etc...

If there are already such mechanism in place, I would be thankfull
for any hints and sorry if I missed something more or less obvious.

Many thanks for your work,
 greetings
  Hermann

P.S: Just noted that in git://anonscm.debian.org/pkg-shinken/shinken.git
since February version 2.2 is available (Thanks, Thibault) and even
2.4-BETA1 is checked in - if those would appear on packages.debian.org,
I think the testing and spreading of shinken will increase.
Will start to test that stuff now.

-- 
Netzwerkadministration/Zentrale Dienste, Interdiziplinaeres 
Zentrum fuer wissenschaftliches Rechnen der Universitaet Heidelberg
IWR; INF 368; 69120 Heidelberg; Tel: (06221)54-8236 Fax: -5224
Email: Her...@iw...

Re: [Shinken-devel] Current work on Livestatus & monitoring checks survey ^^

[nap <nap...@gm...>]

On Wed, Mar 11, 2015 at 3:38 PM, Sven Nierlein <sv...@ni...> wrote:

> Hi Jean,
>
> I am missing an answer for the "What if such "lower" importance checks can
> be hidden by default on the "services" view?"
>
>  - i am using this in thruk already[1]
>
> Cheers ;-),
>  Sven
>
> [1]
> http://thruk.org/documentation/configuration.html#default_service_filter
>
>
Like always you rocks ^^


The idea was to also manage it on the core part, to manage such services in
a light way, and so automatically skip them in lot of part, especially the
basic LS part and only list them if you are listng this specific host. It's
a bit strange as behavior but can tune lot of queries ^^


Jean

Re: [Shinken-devel] Current work on Livestatus & monitoring checks survey ^^

[Sven N. <sv...@ni...>]

Hi Jean,

I am missing an answer for the "What if such "lower" importance checks can be hidden by default on the "services" view?"

 - i am using this in thruk already[1]

Cheers ;-),
 Sven

[1] http://thruk.org/documentation/configuration.html#default_service_filter


On 11.03.2015 15:28, nap wrote:
> Hi,
>
> I'm currently working on a module tuning that an help lot of people here :)
>
> The goal is to make livestatus module (for UIs like Thruk, MK/multisite or Adagios) run better with:
> * manage more queries on the same time
> * use all CPU cores (currently it doesn't)
> * make each queries quicker
>
>
> I did reach the first two items on a POC, and I'm still working on the third one (the hardest one :p )
>
>
> Related to this, I did create a survey focus on monitoring checks and especially important/less important one on the same host:  http://t.co/OGsoMi5thR
>
> Please answer to it and forward it to others admins you know ^^
>
> the goal is to see if allowing two levels of service objects can be a good idea or not (important and less important ones).
>
> I'll do a blog post about it when I'll have enough returns for it :)
>
> You still didn't click on it? so I give you the link again :D
>
> http://t.co/OGsoMi5thR
>
> Thanks a lot :)
>
>
> Jean 
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the 
> conversation now. http://goparallel.sourceforge.net/
>
>
> _______________________________________________
> Shinken-devel mailing list
> Shi...@li...
> https://lists.sourceforge.net/lists/listinfo/shinken-devel

[Shinken-devel] Current work on Livestatus & monitoring checks survey ^^

[nap <nap...@gm...>]

Hi,

I'm currently working on a module tuning that an help lot of people here :)

The goal is to make livestatus module (for UIs like Thruk, MK/multisite or
Adagios) run better with:
* manage more queries on the same time
* use all CPU cores (currently it doesn't)
* make each queries quicker


I did reach the first two items on a POC, and I'm still working on the
third one (the hardest one :p )


Related to this, I did create a survey focus on monitoring checks and
especially important/less important one on the same host:
http://t.co/OGsoMi5thR

Please answer to it and forward it to others admins you know ^^

the goal is to see if allowing two levels of service objects can be a good
idea or not (important and less important ones).

I'll do a blog post about it when I'll have enough returns for it :)

You still didn't click on it? so I give you the link again :D

http://t.co/OGsoMi5thR

Thanks a lot :)


Jean

[Shinken-devel] Freezing time for 2.4!

[Sebastien C. <s.c...@fr...>]

Hi everyone!

This is a simple email to let you know that Shinken master branch is now 
in "freeze". As we mentionned in a previous message, the last month 
before the release is dedicated to bug fixes. 2.4 release should be 
March 31 so this is the last month.

As far as I know, we don't have a release name for 2.4, I hope Jean will 
manage to find some time to do so :)

Changelog and version will be updated soon in order to prepare the real 
release. The 2.4 version is mainly about code cleaning (pep8, setup.py, 
windows folder deletion), code stabilization (bug fix) and a bit of 
documentation.


That's all folks !

Sébastien Coavoux

Re: [Shinken-devel] Disabling Notifications

[nap <nap...@gm...>]

Hi,

(you were not registered in the list so your mail was blocked in
sourceforge).

You can also look at downtime, especially the downtime period parameter for
your hosts :)


Jean

On Mon, Feb 9, 2015 at 7:59 PM, Chris Everest <chr...@gm...>
wrote:

> On Monday, February 9, 2015 at 12:42:29 PM UTC-5, Chris Everest wrote:
>>
>> Hi devs, Please let me know if this is the correct list.  This is more of
>> a 'user' question.
>>
>> Anyway, I know we can disable notifications via shinken.cfg:
>>
>> http://shinken.readthedocs.org/en/latest/03_configuration/configmain-
>> advanced.html#notifications-option
>>
>> However, Is there a way we can talk directly to one of the shinken
>> processes at runtime to disable/enable notifications?  I'm specifically
>> interested in writing some sort of handler to add a scheduled maintenance
>> window to suppress notifications.
>>
>>
> Replying to my own post... I see the new forum is live now. I'll post this
> question there.
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming. The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Shinken-devel mailing list
> Shi...@li...
> https://lists.sourceforge.net/lists/listinfo/shinken-devel
>
>

[Shinken-devel] Looking for former Nagios userss

[Jens-Christoph B. <jc...@li...>]

Hi,

we, the editors of Linux-Magazin, are now looking for users who 
exchanged Nagios with an alternative monitoring system and who are 
willing to talk about that subject. We would be interested in answers of 
the following questions:

1.) How many systems (of which sort) have you once monitored with Nagios?

2.) What points of criticism lead to the substitution of Nagios?

3.) Which alternative solutions do you have examined?

4.) Why do you choose your current solution?

5.) How satisfied are you today?

If you may pass a short answer of these questions to us, please contact 
me under jc...@li...

Jens-Christoph Brendel
Head of Linux-Magazin Online
Deputy Editor-in-Chief Linux-Magazin

-- 
===         J e n s - C h r i s t o p h   B r e n d e l         ===
Redaktionsleiter LM Online,    stellv. Chefredakteur Linux-Magazin
Head of Linux-Magazin Online, Deputy Editor in Chief Linux-Magazin

Computec Media GmbH, a subsidiary of Marquard Media Group
Niederlassung München

Putzbrunner Straße 71
81739 München, Germany

Tel.:  +49 (89) 99 34 11 46
Mobil: +49 (163)  356 256 1
Fax:   +49 (89) 99 34 11 99

E-Mail: jc...@li... <mailto:jc...@li...>

www.linux-magazin.de         <http://www.linux-magazin.de>
www.computec.de              <http://www.computec.de>
www.marquard-media.com       <http://www.marquard-media.com>

Sitz der Gesellschaft und Registergericht: Fürth (HRB 14364)
Geschäftsführer: Rainer Rosenbusch und Hans Ippisch
Umsatzsteuer-Identifikationsnummer: DE 812 575 276

[Shinken-devel] Vote for Shinken before February 3rd

[nap <nap...@gm...>]

Hi,

Like each year, the linuxquestions forum is launching a polling about the
favorite monitoring tool.

We are growing year after year in this poll ^^

so it's time to go vote for Shinken this year too and show your love for
this project ^^

http://www.linuxquestions.org/questions/2014-linuxquestions-org-members-choice-awards-113/network-monitoring-application-of-the-year-4175528397/

Thanks a lot, and soon news about the refactoing phase launched after the
2.2 version ^^


Jean

[Shinken-devel] Achievement : 7900 commits ^^

[nap <nap...@gm...>]

Hi,

I just saw that we did reach 7900 commit on the framework repository
https://github.com/naparuba/shinken ^^

https://pbs.twimg.com/media/B73LTp4IQAE61pT.png

Thanks a lot to all the (numerous) contributors that help us to reach this
in the last 5+ years :D

8K commits will be break for the 2.4 release I think. I'll try to make this
8Kth commit a bit special ;)



Jean