FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Infrastructure

 
 
LinkBack Thread Tools
 
Old 12-02-2010, 08:17 PM
seth vidal
 
Default xmpp based nagios notifications

This is really only relevant for the folks who get the nagios alerts but
I thought it was cool.

I setup a test jabber/xmpp address for fedora services it is:
fedora-svc-test@jabber.org

And then I wrote:
http://skvidal.fedorapeople.org/misc/xmppsend.py

and set the whole thing up on our nagios server(s)

I setup my contacts to add a: skvidal_xmpp contact
with contact email set to my xmpp/jabber address.

Then I added the fedora-svc-test address as a contact in my jabber
client.

And now I get nagios notices as popups in my jabber client(s).

-sv




_______________________________________________
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
 
Old 12-02-2010, 08:26 PM
Jose Manimala
 
Default xmpp based nagios notifications

nice one very useful feature

On Fri, Dec 3, 2010 at 10:17 AM, seth vidal <skvidal@fedoraproject.org> wrote:
> This is really only relevant for the folks who get the nagios alerts but
> I thought it was cool.
>
> I setup a test jabber/xmpp address for fedora services it is:
> fedora-svc-test@jabber.org
>
> And then I wrote:
> http://skvidal.fedorapeople.org/misc/xmppsend.py
>
> and set the whole thing up on our nagios server(s)
>
> I setup my contacts to add a: skvidal_xmpp contact
> with contact email set to my xmpp/jabber address.
>
> Then I added the fedora-svc-test address as a contact in my jabber
> client.
>
> And now I get nagios notices as popups in my jabber client(s).
>
> -sv
>
>
>
>
> _______________________________________________
> infrastructure mailing list
> infrastructure@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/infrastructure
>



--
Cheers
Jose
http://josemanimala.eu.org/blog
Ph: +64221033100
_______________________________________________
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
 
Old 12-02-2010, 09:39 PM
Jeffrey Ollie
 
Default xmpp based nagios notifications

On Thu, Dec 2, 2010 at 3:17 PM, seth vidal <skvidal@fedoraproject.org> wrote:
>
> And now I get nagios notices as popups in my jabber client(s).

On a side note, would it make sense to have a Fedora XMPP server?
That would allow people to use <fas id>@fedoraproject.org as a XMPP
ID. There are a number of good XMPP servers already packaged for
Fedora and/or EPEL, the hard part would be choosing one and figuring
out how to get authentication against FAS working.

--
Jeff Ollie
_______________________________________________
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
 
Old 12-02-2010, 09:42 PM
seth vidal
 
Default xmpp based nagios notifications

On Thu, 2010-12-02 at 16:39 -0600, Jeffrey Ollie wrote:
> On Thu, Dec 2, 2010 at 3:17 PM, seth vidal <skvidal@fedoraproject.org> wrote:
> >
> > And now I get nagios notices as popups in my jabber client(s).
>
> On a side note, would it make sense to have a Fedora XMPP server?
> That would allow people to use <fas id>@fedoraproject.org as a XMPP
> ID. There are a number of good XMPP servers already packaged for
> Fedora and/or EPEL, the hard part would be choosing one and figuring
> out how to get authentication against FAS working.

I don't think it would make sense for us to have our own xmpp server for
users. But it may make sense for us to have our own for services.

there are lots of good, public, free jabber/xmpp servers and there's no
good reason for us to get into that business or the support headaches it
creates.

But for our services it could make sense for us to run one for service
accounts.

What do you think?

-sv



_______________________________________________
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
 
Old 12-03-2010, 02:39 PM
Derek Carter
 
Default xmpp based nagios notifications

On 12/2/10 5:42 PM, seth vidal wrote:
> I don't think it would make sense for us to have our own xmpp server for
> users. But it may make sense for us to have our own for services.
>
> there are lots of good, public, free jabber/xmpp servers and there's no
> good reason for us to get into that business or the support headaches it
> creates.
>
> But for our services it could make sense for us to run one for service
> accounts.
>
> What do you think?

Seth's idea++

--
Derek Carter
aka goozbach
_______________________________________________
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
 
Old 12-06-2010, 01:38 AM
David Nalley
 
Default xmpp based nagios notifications

On Thu, Dec 2, 2010 at 5:42 PM, seth vidal <skvidal@fedoraproject.org> wrote:
> On Thu, 2010-12-02 at 16:39 -0600, Jeffrey Ollie wrote:
>> On Thu, Dec 2, 2010 at 3:17 PM, seth vidal <skvidal@fedoraproject.org> wrote:
>> >
>> > And now I get nagios notices as popups in my jabber client(s).
>>
>> On a side note, would it make sense to have a Fedora XMPP server?
>> That would allow people to use <fas id>@fedoraproject.org as a XMPP
>> ID. *There are a number of good XMPP servers already packaged for
>> Fedora and/or EPEL, the hard part would be choosing one and figuring
>> out how to get authentication against FAS working.
>
> I don't think it would make sense for us to have our own xmpp server for
> users. But it may make sense for us to have our own for services.
>
> there are lots of good, public, free jabber/xmpp servers and there's no
> good reason for us to get into that business or the support headaches it
> creates.
>
> But for our services it could make sense for us to run one for service
> accounts.
>
> What do you think?
>
> -sv


So I have started looking at this - and currently only jabberd (really
jabberd2) and ejabberd are packaged in Fedora and EPEL, which
simplifies things a bit.

jabberd2 is written in C, and appears to have been abandoned 6-7 years
ago, though it seemingly was picked up and is currently maintained by
a single developer. Sadly documentation has not kept pace with
development, and the current documentation is 6-7 years old.

ejabberd is written in erlang, and appears to be one of the better
supported xmpp server implementations. Aside from being written in
erlang, another downside is that it requires either postgres or mysql,
which seems like a bit of overkill for nagios messaging. (jabberd2
supports Berkley and SQLite, which strikes me as lighterweight, but
perhaps it really doesn't matter).

Oddly enough I find myself leaning towards ejabberd, simply because it
appears to be more robustly maintained. I have, in the past, used the
1.x version of jabberd (which is completely different) and ejabberd,
as well as some others that aren't in Fedora atm.

Perhaps we can get this setup rapidly on a testing instance once we
make a server choice.
_______________________________________________
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
 
Old 12-06-2010, 02:00 AM
seth vidal
 
Default xmpp based nagios notifications

On Sun, 2010-12-05 at 21:38 -0500, David Nalley wrote:
> On Thu, Dec 2, 2010 at 5:42 PM, seth vidal <skvidal@fedoraproject.org> wrote:
> > On Thu, 2010-12-02 at 16:39 -0600, Jeffrey Ollie wrote:
> >> On Thu, Dec 2, 2010 at 3:17 PM, seth vidal <skvidal@fedoraproject.org> wrote:
> >> >
> >> > And now I get nagios notices as popups in my jabber client(s).
> >>
> >> On a side note, would it make sense to have a Fedora XMPP server?
> >> That would allow people to use <fas id>@fedoraproject.org as a XMPP
> >> ID. There are a number of good XMPP servers already packaged for
> >> Fedora and/or EPEL, the hard part would be choosing one and figuring
> >> out how to get authentication against FAS working.
> >
> > I don't think it would make sense for us to have our own xmpp server for
> > users. But it may make sense for us to have our own for services.
> >
> > there are lots of good, public, free jabber/xmpp servers and there's no
> > good reason for us to get into that business or the support headaches it
> > creates.
> >
> > But for our services it could make sense for us to run one for service
> > accounts.
> >
> > What do you think?
> >
> > -sv
>
>
> So I have started looking at this - and currently only jabberd (really
> jabberd2) and ejabberd are packaged in Fedora and EPEL, which
> simplifies things a bit.
>
> jabberd2 is written in C, and appears to have been abandoned 6-7 years
> ago, though it seemingly was picked up and is currently maintained by
> a single developer. Sadly documentation has not kept pace with
> development, and the current documentation is 6-7 years old.
>
> ejabberd is written in erlang, and appears to be one of the better
> supported xmpp server implementations. Aside from being written in
> erlang, another downside is that it requires either postgres or mysql,
> which seems like a bit of overkill for nagios messaging. (jabberd2
> supports Berkley and SQLite, which strikes me as lighterweight, but
> perhaps it really doesn't matter).
>
> Oddly enough I find myself leaning towards ejabberd, simply because it
> appears to be more robustly maintained. I have, in the past, used the
> 1.x version of jabberd (which is completely different) and ejabberd,
> as well as some others that aren't in Fedora atm.
>
> Perhaps we can get this setup rapidly on a testing instance once we
> make a server choice.

I thought there was a jabberd implemention in lua call prosody.im ?

-sv


_______________________________________________
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
 
Old 12-06-2010, 02:12 AM
David Nalley
 
Default xmpp based nagios notifications

On Sun, Dec 5, 2010 at 10:00 PM, seth vidal <skvidal@fedoraproject.org> wrote:
> On Sun, 2010-12-05 at 21:38 -0500, David Nalley wrote:
>> On Thu, Dec 2, 2010 at 5:42 PM, seth vidal <skvidal@fedoraproject.org> wrote:
>> > On Thu, 2010-12-02 at 16:39 -0600, Jeffrey Ollie wrote:
>> >> On Thu, Dec 2, 2010 at 3:17 PM, seth vidal <skvidal@fedoraproject.org> wrote:
>> >> >
>> >> > And now I get nagios notices as popups in my jabber client(s).
>> >>
>> >> On a side note, would it make sense to have a Fedora XMPP server?
>> >> That would allow people to use <fas id>@fedoraproject.org as a XMPP
>> >> ID. *There are a number of good XMPP servers already packaged for
>> >> Fedora and/or EPEL, the hard part would be choosing one and figuring
>> >> out how to get authentication against FAS working.
>> >
>> > I don't think it would make sense for us to have our own xmpp server for
>> > users. But it may make sense for us to have our own for services.
>> >
>> > there are lots of good, public, free jabber/xmpp servers and there's no
>> > good reason for us to get into that business or the support headaches it
>> > creates.
>> >
>> > But for our services it could make sense for us to run one for service
>> > accounts.
>> >
>> > What do you think?
>> >
>> > -sv
>>
>>
>> So I have started looking at this - and currently only jabberd (really
>> jabberd2) and ejabberd are packaged in Fedora and EPEL, which
>> simplifies things a bit.
>>
>> jabberd2 is written in C, and appears to have been abandoned 6-7 years
>> ago, though it seemingly was picked up and is currently maintained by
>> a single developer. Sadly documentation has not kept pace with
>> development, and the current documentation is 6-7 years old.
>>
>> ejabberd is written in erlang, and appears to be one of the better
>> supported xmpp server implementations. Aside from being written in
>> erlang, another downside is that it requires either postgres or mysql,
>> which seems like a bit of overkill for nagios messaging. (jabberd2
>> supports Berkley and SQLite, which strikes me as lighterweight, but
>> perhaps it really doesn't matter).
>>
>> Oddly enough I find myself leaning towards ejabberd, simply because it
>> appears to be more robustly maintained. I have, in the past, used the
>> 1.x version of jabberd (which is completely different) and ejabberd,
>> as well as some others that aren't in Fedora atm.
>>
>> Perhaps we can get this setup rapidly on a testing instance once we
>> make a server choice.
>
> I thought there was a jabberd implemention in lua call prosody.im ?
>
> -sv

There is - I don't see it in either EPEL or Fedora's repos though,
which was one of my search constraints.
_______________________________________________
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
 
Old 12-06-2010, 04:16 AM
Jeffrey Ollie
 
Default xmpp based nagios notifications

On Sun, Dec 5, 2010 at 8:38 PM, David Nalley <david@gnsa.us> wrote:
>
> ejabberd is written in erlang, and appears to be one of the better
> supported xmpp server implementations. Aside from being written in
> erlang,

Erlang is actually a pretty interesting language, especially for
writing network servers. However there is the downside that I doubt
many people on the Infrastructure team are familiar with Erlang and
having some familiarity definitely helps out when configuring or
troubleshooting Ejabberd.

> another downside is that it requires either postgres or mysql,

Where do you see this requirement? I'm not a ejabberd guru but as far
as I know ejabberd does not require postgresql or mysql, it will use
Erlang's built in database (MNESIA). The servers that I run at
$DAYJOB use LDAP as the user store and never touch a postgresql or
mysql server.

> Oddly enough I find myself leaning towards ejabberd, simply because it
> appears to be more robustly maintained. I have, in the past, used the
> 1.x version of jabberd (which is completely different) and ejabberd,
> as well as some others that aren't in Fedora atm.

Ejabberd is my preference too, but since I doubt I'll be able to do a
whole lot to help out don't let my opinion get in the way.

One other testimonial is that Facebook uses Ejabbed behind the scenes
to handle their chat service...

> Perhaps we can get this setup rapidly on a testing instance once we
> make a server choice.

Either Ejabberd or Jabberd2 are pretty easy to set up, at least in a
standalone single-node mode.

--
Jeff Ollie
_______________________________________________
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
 
Old 12-06-2010, 04:38 AM
David Nalley
 
Default xmpp based nagios notifications

On Mon, Dec 6, 2010 at 12:16 AM, Jeffrey Ollie <jeff@ocjtech.us> wrote:
> On Sun, Dec 5, 2010 at 8:38 PM, David Nalley <david@gnsa.us> wrote:
>>
>> ejabberd is written in erlang, and appears to be one of the better
>> supported xmpp server implementations. Aside from being written in
>> erlang,
>
> Erlang is actually a pretty interesting language, especially for
> writing network servers. *However there is the downside that I doubt
> many people on the Infrastructure team are familiar with Erlang and
> having some familiarity definitely helps out when configuring or
> troubleshooting Ejabberd.

Yeah, that's my concern

>
>> another downside is that it requires either postgres or mysql,
>
> Where do you see this requirement? *I'm not a ejabberd guru but as far
> as I know ejabberd does not require postgresql or mysql, it will use
> Erlang's built in database (MNESIA). *The servers that I run at
> $DAYJOB use LDAP as the user store and never touch a postgresql or
> mysql server.

hmmm perhaps I read docs wrong then.

>
>> Oddly enough I find myself leaning towards ejabberd, simply because it
>> appears to be more robustly maintained. I have, in the past, used the
>> 1.x version of jabberd (which is completely different) and ejabberd,
>> as well as some others that aren't in Fedora atm.
>
> Ejabberd is my preference too, but since I doubt I'll be able to do a
> whole lot to help out don't let my opinion get in the way.
>
> One other testimonial is that Facebook uses Ejabbed behind the scenes
> to handle their chat service...

Yeah, I understand jabber.org uses it as well now.

>
>> Perhaps we can get this setup rapidly on a testing instance once we
>> make a server choice.
>
> Either Ejabberd or Jabberd2 are pretty easy to set up, at least in a
> standalone single-node mode.
>
_______________________________________________
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
 

Thread Tools




All times are GMT. The time now is 08:27 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org