[Standards] Event Logging over XMPP

Peter Waher Peter.Waher at clayster.com
Sun Nov 10 14:37:55 UTC 2013

Hello Steffen

I would prefer not to use JSON as I want to include this in resource constrained environments. They already have sufficient problems implementing XML parsers, and to include JSON parses as well (for no apparent reason) would just be a waste of precious bytes in a small device. Furthermore, using JSON is like check-mating the entire idea by using XML in XMPP in the first place: plugability using namespaces, easy to validate (schema), search (XPath) and version handling and transformations (XSLT). I understand javascript clients are fond of JSON, but as a protocol to send tagged and interoperable data, I would choose XML.

However, having said that, we should collect a set of appropriate fields/attributes (as in your example) that must go into such a message for it to be useful.

Best regards,
Peter Waher

From: Steffen Larsen [mailto:zooldk at gmail.com]
Sent: den 10 november 2013 07:19
To: XMPP Standards
Subject: Re: [Standards] Event Logging over XMPP

Hi Bear et al,

Yes I was thinking of the same thing. I've done it in a different way now, but using log stash just means to embedded the JSON into the stanza.
Because I am using logstash/kibana (elastic search, http://www.elasticsearch.org/overview/kibana/) for my customers so that would be straight forward. Maybe a message stanza like this?:

<message to="logger at mydomain.tld<mailto:logger at mydomain.tld>">
<json xmlns="urn:xmpp:json:0>

or if you do not want to embed it into the body but in a separate container instead:

<message to="logger at mydomain.tld<mailto:logger at mydomain.tld>">
<json xmlns="urn:xmpp:json:0>

In the receiving part (logger at mydomain.tld<mailto:logger at mydomain.tld>) it could either be a component or a simple bot, that either appended the embedded json into a file and logstashd would take it, or a component that would queue it directly to rabbitmq which in my example would feed it to logstash/kibana.

I am already using logstash and graphite for my XMPP servers, its nice to have a visual overview and graphs when handling large scale XMPP... Hmmmm maybe I could use that as a topic for FOSDEM?


On 09 Nov 2013, at 21:20, Mike Taylor <bear at bear.im<mailto:bear at bear.im>> wrote:

Hash: SHA1

On 11/09/2013 03:13 PM, Robert Kosten wrote:

Hi, a Lurker here ;-)

I've had the same thought about two years ago as well so I
implemented a small Monolog (PHP Logging Library) Handler that sent
log messages as both formatted message (for standard chat clients)
and a custom stanza for our status board. At the time I thought
that pub/sub might actually be better though, because I didn't
really want the logger to know who would receive the message...

Sadly that code belongs to a former company and I'm not certain I
can remember everything about it (It was a quick'n'dirty
solution), otherwise I'd attach it :-P

Regards, Robert Kosten

On 11/09/2013 09:08 PM, Steffen Larsen wrote:

No haven't seen such a XEP, but I've implemented something like
it to be able to remote debug set-top boxes etc. I've just did a
dumb implementation based on message stanzas, where the client
can send the log to diff. implementations like console, remote
(xmpp), file etc. with different levels.

So I am interested as well. :-)

I could see this happening by wrapping the "protocol" that Logstash uses.


On 09 Nov 2013, at 19:30, Matthew Wild <mwild1 at gmail.com<mailto:mwild1 at gmail.com>> wrote:

On 9 November 2013 18:24, Peter Waher
<Peter.Waher at clayster.com<mailto:Peter.Waher at clayster.com>> wrote:


Is anybody aware of event logging extensions for XMPP? XEP
0163, 207 and 316 all relate to publish/subscript (personal)
events as I can see. What I'm looking for is system and
network events for system administrators, like Syslog, for
instance, but over XMPP.

No, but I have wished for such a XEP before now. I'd love to
see a simple one that primarily defines a way to transport log
messages over XMPP (perhaps re-using syslog semantics).

Regards, Matthew

- --

xmpp agitator; ops curmudgeon; generalist
0A93 9BA7 8203 FCBC 58A9 E8B5 9D1E 0661 8EE5 B4D8
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20131110/d2301c88/attachment.html>

More information about the Standards mailing list