I was thinking about syslog-syslog (sorry I will focus on the others
soon:-) and found that we are missing an opportunity...
Currently syslog only uses 24 facilities. Of which 15 are defined. And
are more or less "old". There are 8 facilities, which anybody can use,
but nobody know when en which. (The 8 local ones).
For routers and other network related stuff, it will do. But syslog is
also heavily used to log applications.
And as the facilities are coded in to a 3digit PRI, lets use the
momentum of this RFC to extent the set of facilities!
(let's face it, nobody is using a byte anymore tho store the PRI. Not
even in small software! I know, I used to write that software...)
So I suggest to use-up the space of 3 digits and specify (999/8) upto
120 facilities.
I know, we are describing the current use. But we can easily extent
it, as long as we don't break anything. And the isn't a rule about
"what to to if facility is bigger then local7. ... Probably it just
work even when not specified.
I think al current facilities should be described as MUST
implement. The new-ones as SHOULD for relays en collectors and as MAY
for devices.
To structer the new ones, I suggest to code the diggits, like e.g. the
errorcodes in several other protocols
So the list of facilities becomes:
Numerical code Facility
Code
0 kernel messages
... as in the draft ...
23 local use 7 (local7)
24-29 local use 8-13
3* Web application
4* Financial application
5* Legal application
7* database application
8* engineering application
9*.. 11* I HAVE NO CLUE; PLEASE ADD SOME
120-
*0 generic
*1 server-side
*2 client-side
*3 middleware
*4-6 WE NEED TO ADD THEM
*7-9 local-extension 1/2/3
Please comment
ALbert
---GAM
"This should be a jolly quote"
====
Do NOT send MS-Word or other MS-bits to me!
I can read them now, but I still don't like it.
