MonitorWare Knowledge Base

template code... its just an alias for the real ones

• Custom phpLogCon configuration?
• Maintenance Contract?
• Installation support?

rgerhards wrote:It's clean, but I think it would be better to work on a scheme similar to rsyslog. Rsyslog already has fields defined in its property replacer:

http://www.rsyslog.com/doc-property_replacer.html

However, they are ugly - but known by users.

Do we have samples of the format if each property somewhere?

alorbach wrote:template code... its just an alias for the real ones

mmmhhhh... The whole point was that users do not need to relearn the properties. Isn't that contradictionary? Or does the user not get in touch with the template?

alorbach wrote:

rgerhards wrote:It's clean, but I think it would be better to work on a scheme similar to rsyslog. Rsyslog already has fields defined in its property replacer:

http://www.rsyslog.com/doc-property_replacer.html

However, they are ugly - but known by users.

Do we have samples of the format if each property somewhere?

What do you mean with "samples of the format"? If they are strings or numbers?

How is the date is formatted for example. Is it a unix timestamp, or something like "Feb 11 11:06:54"?

rgerhards wrote:

alorbach wrote:template code... its just an alias for the real ones

mmmhhhh... The whole point was that users do not need to relearn the properties. Isn't that contradictionary? Or does the user not get in touch with the template?

I don't see how the user is related to the templace coding, unless he wants to MOD phplogcon. I am not talking about the display names in the grid. It's all about the template coding ^^

ok, than this sounds good. As a side-note, I am thinking if we should use the new (much friendlier) names in rsyslog expressions. That would probably be the last chance the change things. I think I'll discuss this with the rsyslog community, too.