<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.network.shinken.devel">
    <title>gmane.network.shinken.devel</title>
    <link>http://permalink.gmane.org/gmane.network.shinken.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.shinken.devel/1864"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.shinken.devel/1863"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.shinken.devel/1862"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.shinken.devel/1861"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.shinken.devel/1860"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.shinken.devel/1859"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.shinken.devel/1858"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.shinken.devel/1857"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.shinken.devel/1856"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.shinken.devel/1855"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.shinken.devel/1854"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.shinken.devel/1853"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.shinken.devel/1852"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.shinken.devel/1851"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.shinken.devel/1850"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.shinken.devel/1849"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.shinken.devel/1848"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.shinken.devel/1847"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.shinken.devel/1846"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.shinken.devel/1845"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.network.shinken.devel/1864">
    <title>Re: Here is the 1.4RC1 :)</title>
    <link>http://permalink.gmane.org/gmane.network.shinken.devel/1864</link>
    <description>&lt;pre&gt;Hi all,

a short update on this:


I reinstalled from scratch on a up-to-date Ubuntu 12.04 VM.

The login breaks after issuing `./install -a nconf` and restarting
Shinken via `/etc/init.d/shinken restart`.

Here's an excerpt of the logs (scheduler and broker at DEBUG level) of
a failed login attempt:

    ==&amp;gt; var/schedulerd.log &amp;lt;==
    2013-06-07 10:23:34,428 [1370600614] Debug :   Load: (sleep) 1.00
(average: 1.00) -&amp;gt; 0%
    2013-06-07 10:23:34,428 [1370600614] Debug :   hook_point:
PickleRetention: False get_new_actions
    2013-06-07 10:23:34,429 [1370600614] Debug :   hook_point:
PickleRetention: False get_new_actions
    2013-06-07 10:23:34,429 [1370600614] Debug :   Time to send 0
broks (after 0 secs)
    2013-06-07 10:23:34,429 [1370600614] Debug :   Checks: total 0,
scheduled 0, inpoller 0, zombies 0, notifications 0
    2013-06-07 10:23:34,430 [1370600614] Debug :   Check average = 0 checks/s

    ==&amp;gt; var/brokerd.log &amp;lt;==
    2013-06-07 10:23:34,643 Added task (0 tasks queued)
    2013-06-07 10:23:34&lt;/pre&gt;</description>
    <dc:creator>Riccardo Murri</dc:creator>
    <dc:date>2013-06-07T15:14:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.shinken.devel/1863">
    <title>1.6 will be 2.0 :)</title>
    <link>http://permalink.gmane.org/gmane.network.shinken.devel/1863</link>
    <description>&lt;pre&gt;Hi all,

I start to hack the master tree for the new modules layout. Now it pass all
tests, but it add a new mandatory parameter for the configuration.

I think with the change that will occurs, it won't be a simple update, but
a more deep change. So It won't be a 1.6 version, but a 2.0 one.

I think we will also change the project vision. The "all in one solution"
was maybe too much. What make us happy to code is when we add a new feature
or thing like the new shinken.io website, not to hack again and again the
install script to manage more and more add-ons.

The new version will be also a way to change this, and to make us focus on
where Shinken is really great : distributed env and flexibility. So I'll
propose soon a new vision, with no more a "monitoring solution" point of
view, but more with a "monitoring framework" one.

Numerous trainees around the world will hate me for doing this, but I think
we should more focus on making devops job easier, than to help a trainee to
install a tool without having to&lt;/pre&gt;</description>
    <dc:creator>nap</dc:creator>
    <dc:date>2013-06-05T15:04:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.shinken.devel/1862">
    <title>Re: Here is the 1.4RC1 :)</title>
    <link>http://permalink.gmane.org/gmane.network.shinken.devel/1862</link>
    <description>&lt;pre&gt;
it solve your problem, we will definitely change the install script :p


Jean
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j_______________________________________________
Shinken-devel mailing list
Shinken-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/shinken-devel
&lt;/pre&gt;</description>
    <dc:creator>nap</dc:creator>
    <dc:date>2013-06-03T18:53:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.shinken.devel/1861">
    <title>Re: Here is the 1.4RC1 :)</title>
    <link>http://permalink.gmane.org/gmane.network.shinken.devel/1861</link>
    <description>&lt;pre&gt;Hi,

On 3 June 2013 15:44, nap &amp;lt;naparuba-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:

Thanks for the suggestion -- I'll try it next week when I'm back to office.
Anyway, the message was for a 1.4rc1 deployed with the `./install` script
on a vanilla Ubuntu 12.04.2.  So, if `python-twisted` is there instead of
`python-paste`, it's likely because the installation script chose
twisted over paste ;-)

Thanks,
Riccardo

------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with &amp;lt;2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
&lt;/pre&gt;</description>
    <dc:creator>Riccardo Murri</dc:creator>
    <dc:date>2013-06-03T16:12:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.shinken.devel/1860">
    <title>Re: Here is the 1.4RC1 :)</title>
    <link>http://permalink.gmane.org/gmane.network.shinken.devel/1860</link>
    <description>&lt;pre&gt;Hi,

On 1 June 2013 02:21, Jean-Michel Collongette &amp;lt;jean.mich.c-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:

This is on 1.4rc1, installed from scratch on a test server.


I'm off-site this week, I'll try to debug the issue further that next
week and post the result.

Thanks,
Riccardo

------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with &amp;lt;2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
&lt;/pre&gt;</description>
    <dc:creator>Riccardo Murri</dc:creator>
    <dc:date>2013-06-03T16:09:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.shinken.devel/1859">
    <title>Re: Here is the 1.4RC1 :)</title>
    <link>http://permalink.gmane.org/gmane.network.shinken.devel/1859</link>
    <description>&lt;pre&gt;I saw problems with the twisted backend. If you can, remove twited and
install python-paste instead.


Jean
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with &amp;lt;2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2_______________________________________________
Shinken-devel mailing list
Shinken-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/shinken-devel
&lt;/pre&gt;</description>
    <dc:creator>nap</dc:creator>
    <dc:date>2013-06-03T13:44:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.shinken.devel/1858">
    <title>Re: Road to 1.6</title>
    <link>http://permalink.gmane.org/gmane.network.shinken.devel/1858</link>
    <description>&lt;pre&gt;
Hi,


plan to work on this before the new protocol backend is ready of course.


possible), but not for core.

a new index on the devel branch that can help mongodb setups.

on modules management from the core, not on modules directly yes.

large ones that will take times before being ok. I openend a branch-1.4 for
the 1.4.1 if need, we will be able to cherrypick bug fix there is need (so
bug fixes SHOULD be on master, then we will backeport them on this branch).
I give a try to this way to see if it's not too much work. If it is not, we
can keep it.


Jean
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with &amp;lt;2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2_______________________________________________
Shinken-devel mailing list
Shinken-devel-5NWGOfrQm&lt;/pre&gt;</description>
    <dc:creator>nap</dc:creator>
    <dc:date>2013-06-03T13:24:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.shinken.devel/1857">
    <title>Re: Road to 1.6</title>
    <link>http://permalink.gmane.org/gmane.network.shinken.devel/1857</link>
    <description>&lt;pre&gt;Hi,

lot of questions indeed :D

On Fri, May 31, 2013 at 2:43 PM, Imrane DESSAI &amp;lt;dessai.imrane-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt;wrote:

For each feature, I always got a phase where I describe it on paper, with
numerous corners cases. I didn't finish this phase, so only major parts
will be available here, don't wait for a real finished RFC, but more for
proposal that can be changed if we see some troubles adead :)


It we can yes. The problem is not really the scripts, but the dependencies
(like my script need python-mysql on debian and libmysql on RedHat, things
like this). It can be great to manage this, but I think it will work
flawlessly only on few distro (I think we should focus on RedHat6/7 and
debian/ubuntu only).

Many time, a pack comes with its own plugin
It mainly depends on the dev here, or if the people taht are doing the pack
are the main dev or someone else. For core packs, it will be the same
repository "because we can" :)


cf my previous points.

I prefer that we stick to a "describe&lt;/pre&gt;</description>
    <dc:creator>nap</dc:creator>
    <dc:date>2013-06-03T13:19:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.shinken.devel/1856">
    <title>Re: Road to 1.6</title>
    <link>http://permalink.gmane.org/gmane.network.shinken.devel/1856</link>
    <description>&lt;pre&gt;Hi everybody,
Last month I sourced out the shinken plugin (check_shinken) to a separate repository [1].

I think splitting packs, modules and Shinken specific plugins from the core is the first step on the way to 1.6.

[1] https://github.com/shinken-monitoring/check_shinken

Andreas

Am 01.06.2013 um 03:32 schrieb Francois Mikus &amp;lt;fmikus-bOls9rUoq0FWk0Htik3J/w&amp;lt; at &amp;gt;public.gmane.org&amp;gt;:


------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with &amp;lt;2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2_______________________________________________
Shinken-devel mailing list
Shinken-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/shinken-devel
&lt;/pre&gt;</description>
    <dc:creator>Frescha</dc:creator>
    <dc:date>2013-06-01T16:43:28</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.shinken.devel/1855">
    <title>Re: Road to 1.6</title>
    <link>http://permalink.gmane.org/gmane.network.shinken.devel/1855</link>
    <description>&lt;pre&gt;Hello,

For Shinken 1.6:

 1. Re-implement check_shinken to actually use PYRO to talk to each
    daemon and get pertinent statistics to actually determine that a
    daemon is really running. The same logic would apply to the arbiter,
    the current "ping" is inadequate and leads to cases where daemons
    are actually not doing what they are supposed to. Identify key
    metrics for each daemon, implement a function to expose them and
    rewrite check_shinken to use it.
 2. Splitting packs, modules and core is a good idea, I have no opinion
    on how to go about doing this, but things seem to be looking up. Go
    team.
 3. Implement RPN + logic functions for bug-less triggers. We will be
    working on this.
 4. Optimize Mongodb logstore functions for Livestatus so that it is
    actually usable in large installations. So that we can finally drop
    sqlite.
 5. -1 for Implementing more database back ends. We should focus on
    making what we have work well.
 6. Focus on a solid 1.6 release with bug f&lt;/pre&gt;</description>
    <dc:creator>Francois Mikus</dc:creator>
    <dc:date>2013-06-01T01:32:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.shinken.devel/1854">
    <title>Re: "tactical overview" in WebUI</title>
    <link>http://permalink.gmane.org/gmane.network.shinken.devel/1854</link>
    <description>&lt;pre&gt;Correct me if i'm wrong, this kind of page exist already.....

i don't remember this URL or the way to see it in webUI, but i am sure it
displays a clock and ok/critital stuff


2013/5/16 Frescha &amp;lt;frescha-wqL4EIc7g5PmnL8Y2IFfrQ&amp;lt; at &amp;gt;public.gmane.org&amp;gt;



&lt;/pre&gt;</description>
    <dc:creator>Jean-Michel Collongette</dc:creator>
    <dc:date>2013-06-01T00:25:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.shinken.devel/1853">
    <title>Re: Here is the 1.4RC1 :)</title>
    <link>http://permalink.gmane.org/gmane.network.shinken.devel/1853</link>
    <description>&lt;pre&gt;Hi,

is the problem steel here?

This happend for me on 1.01 if i'm right, try to reinstall from scratch, it
worked for me.

Otherwise, could you paste the debug log from scheduler on logging attempt?

nero


2013/5/16 Riccardo Murri &amp;lt;riccardo.murri-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt;




&lt;/pre&gt;</description>
    <dc:creator>Jean-Michel Collongette</dc:creator>
    <dc:date>2013-06-01T00:21:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.shinken.devel/1852">
    <title>Re: distributed arch: security and bandwith ?</title>
    <link>http://permalink.gmane.org/gmane.network.shinken.devel/1852</link>
    <description>&lt;pre&gt;Hi,

sites will be to set up a VPN (like IPSEC), or suscribe an LS from your
operator.

This should be much better/safer than ..."i don't know you do this from
now?? :)" , and will improve your netwok arch.

That way everything is transmitted throught a private network, no need to
implement SSL.

I use a like arch over 16 sites with various bandwith, SDSL,ASDL,100MB/fc...

nero


2013/5/16 Adrien Grellier &amp;lt;adrien.grellier-be2bQWTIkeNvynnTyRI/EA&amp;lt; at &amp;gt;public.gmane.org&amp;gt;




&lt;/pre&gt;</description>
    <dc:creator>Jean-Michel Collongette</dc:creator>
    <dc:date>2013-06-01T00:15:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.shinken.devel/1851">
    <title>Re: Road to 1.6</title>
    <link>http://permalink.gmane.org/gmane.network.shinken.devel/1851</link>
    <description>&lt;pre&gt;I saw your first commit about this.

Have you some time to explain how concretely you will manage packs and
modules ?

Where plugins (scripts) would be stored ?
Many time, a pack comes with its own plugin
Should we work with the plugin separately from the pack it belongs to ?
Can we include the plugin into the pack ?
If yes, what about plugin that needs install script (for dependancies ...)
Packs will changedir from etc ?
How to manage custom packs/modules without overwriting existing
packs/modules ? (so that we don't have to fear a module/packs update) ?
How to upgrade shinken from previous version (1.2.4 or 1.4 to 1.6) ?

Last but not least, how can we help with this ?
 Will you create multiple small task that everyone can contribute to ?
For example :
  To achieve this first part, here are 5 small "git hub issue" to be solved
?
   Then we can attack the second part that contains 10 small task ...
Or you will code all and ask for tests ?

I know, it's too many questions :s




2013/5/31 nap &amp;lt;naparuba-Re5JQ&lt;/pre&gt;</description>
    <dc:creator>Imrane DESSAI</dc:creator>
    <dc:date>2013-05-31T12:43:28</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.shinken.devel/1850">
    <title>Re: Road to 1.6</title>
    <link>http://permalink.gmane.org/gmane.network.shinken.devel/1850</link>
    <description>&lt;pre&gt;On Fri, May 31, 2013 at 2:03 PM, Jean-Michel Collongette &amp;lt;
jean.mich.c-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:


That's also one important thing for external packs and modules : they can
have their own release schedule. Some modules got lot and lot enhancements,
but are only "release" with the full stack. It's quite the same with
modules.


Jean
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with &amp;lt;2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2_______________________________________________
Shinken-devel mailing list
Shinken-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/shinken-devel
&lt;/pre&gt;</description>
    <dc:creator>nap</dc:creator>
    <dc:date>2013-05-31T12:10:20</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.shinken.devel/1849">
    <title>Re: Road to 1.6</title>
    <link>http://permalink.gmane.org/gmane.network.shinken.devel/1849</link>
    <description>&lt;pre&gt;Hi,

I agree to separe the packs from the shinken core.

This way could be easy to manage enhancement and upgrade of single packs
instead of wall of them currently.

nero


2013/5/15 Imrane DESSAI &amp;lt;dessai.imrane-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt;



&lt;/pre&gt;</description>
    <dc:creator>Jean-Michel Collongette</dc:creator>
    <dc:date>2013-05-31T12:03:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.shinken.devel/1848">
    <title>Re: Ready? Time to upgrade to 1.4! :D</title>
    <link>http://permalink.gmane.org/gmane.network.shinken.devel/1848</link>
    <description>&lt;pre&gt;

We change the announce format thanks to Andreas. It is more simpler and
focus on what is central in the release. If we got good return from this
test, we will keep this format for the new ones :)


Jean
------------------------------------------------------------------------------
Try New Relic Now &amp;amp; We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, &amp;amp; servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may_______________________________________________
Shinken-devel mailing list
Shinken-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/shinken-devel
&lt;/pre&gt;</description>
    <dc:creator>nap</dc:creator>
    <dc:date>2013-05-27T14:39:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.shinken.devel/1847">
    <title>Re: Ready? Time to upgrade to 1.4! :D</title>
    <link>http://permalink.gmane.org/gmane.network.shinken.devel/1847</link>
    <description>&lt;pre&gt;Congratulations for this new release, a lot of new interestings features,
can't wait to test it.

&lt;/pre&gt;</description>
    <dc:creator>Gwenole Le Bris</dc:creator>
    <dc:date>2013-05-27T13:34:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.shinken.devel/1846">
    <title>Re: Ready? Time to upgrade to 1.4! :D</title>
    <link>http://permalink.gmane.org/gmane.network.shinken.devel/1846</link>
    <description>&lt;pre&gt;Awesome !

Great job done by the whole team : core dev and contributors.

Making new release shorter will help Shinken a lot, I think


2013/5/27 nap &amp;lt;naparuba-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt;

------------------------------------------------------------------------------
Try New Relic Now &amp;amp; We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, &amp;amp; servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may_______________________________________________
Shinken-devel mailing list
Shinken-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/shinken-devel
&lt;/pre&gt;</description>
    <dc:creator>Imrane DESSAI</dc:creator>
    <dc:date>2013-05-27T13:26:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.shinken.devel/1845">
    <title>Ready? Time to upgrade to 1.4! :D</title>
    <link>http://permalink.gmane.org/gmane.network.shinken.devel/1845</link>
    <description>&lt;pre&gt;Hi,


After more than 850 commits since the 1.2 versions, here is the 1.4 one!
The version was scheduled for Saturday, but after some last minutes fix,
here it comes :)

If you want to have a close looks at changes, look at the Changelog
https://github.com/naparuba/shinken/blob/master/Changelog

Aside the AWS/EC2 import module, we can see lot of fixes in the WebUI side
thanks to Frescha, and fixes and enhancements to the defaults packs thanks
to Olivier.H and Dessailmrane. Thanks a lot guys :)

About more core features, we can see a huge enhancements in the Broker
architecture, with the multi-levels brokers. The other big feature is the
macro_modulations. It's a good way to modulate alerts level based on the
timeperiod. Thanks to all that help this to become possible, with ideas and
feedbacks! :)

So not it's time to look at the next version. This one won't be a "killer
feature" one I think. This will came back to what make Shinken so powerful
: flexibility. If you follow the latest threads, you know where t&lt;/pre&gt;</description>
    <dc:creator>nap</dc:creator>
    <dc:date>2013-05-27T12:15:00</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.shinken.devel/1844">
    <title>Re: 1.4 is for this week-end</title>
    <link>http://permalink.gmane.org/gmane.network.shinken.devel/1844</link>
    <description>&lt;pre&gt;

No so minor in fact; because it will cause problems between the python
mongo lib and the server. I'll try to fix it before 1.4 so :)

We got another fix in a pull request :
https://github.com/naparuba/shinken/pull/859 it fix perfdata with spaces in
names into the Graphite modules. I can't test it this week-end, only
monday, but if someone got a graphite server and can test it, we can merge
it before monday :)

If not, the 1.4will have 2 days delay so :)


Jean
------------------------------------------------------------------------------
Try New Relic Now &amp;amp; We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, &amp;amp; servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may_______________________________________________
Shinken-devel mailing list
Shinken-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.&lt;/pre&gt;</description>
    <dc:creator>nap</dc:creator>
    <dc:date>2013-05-25T09:04:39</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.network.shinken.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.network.shinken.devel</link>
  </textinput>
</rdf:RDF>
