Boost logo

Boost Users :

Subject: [Boost-users] [Log] Writing empty messages with the attributes as the actual payload
From: Scott Mueller (smueller_at_[hidden])
Date: 2014-10-17 17:28:46


Hello Boost.Users!

I'm trying to integrate Boost logging with an existing message infrastructure. In this infrastructure, I have an existing schema that looks like this:
Severity
Timestamp
Process source (much like "channel")
Process component (more like a "sub-channel")
Message ID
A vector of arguments

The message is rendered by looking up the message ID to receive the following information: formatting string ("This is an example of %1 message type. The arguments can look like this %4, 3, 2"), the expected argument types which are potentially convertible if the underlying type is different, and so on. I guess what I'm asking is whether or not a logging source can accept the arguments as defined by a compile-time defined schema in the form of attributes with an empty message. Can the logging core route message records defined in this way properly? Is such a thing supported?

I'm in the process of writing something up to do this, but I'd like to know in advance whether or not "empty" messages with a bunch of attributes set can get routed to supported sinks.

Thanks in advance for your help!

Best regards,

M. Scott Mueller



Boost-users list run by williamkempf at hotmail.com, kalb at libertysoft.com, bjorn.karlsson at readsoft.com, gregod at cs.rpi.edu, wekempf at cox.net