configuration/org.eclipse.equinox.simpleconfigurator/bundles.info - to add my appender implementation fragment to logback.
configuration/org.ecilpse.virgo.kernel.userregion.properties - to allow my fragment to bleed through to the user region so that my application can change logging parameters at run time
configuration/serviceability.xml - to register my appenders/loggers

According to the documentation one updates serviceability.xml to change configuration of the logback back-end.

What I'm wondering is if there is a way to extend this configuration on a per-application basis without touching that one file. I guess what I'm hoping to avoid are problems where multiple applications are reaching their grimy hands into that configuration file (and other configuration files) to do things like change "logger" settings or add "appender" implementations.

Right now, I'm touching these files to add my own appender:

• configuration/org.eclipse.equinox.simpleconfigurator/bundles.info - to add my appender implementation fragment to logback.
  

• configuration/org.ecilpse.virgo.kernel.userregion.properties - to allow my fragment to bleed through to the user region so that my application can change logging parameters at run time
  
• configuration/serviceability.xml - to register my appenders/loggers
  

Is there any way to avoid this? Any way to package and deploy this with my application/plan?

Medic-LoggingConfiguration: my.logging.config.id

org.eclipse.virgo.medic.log.configuration.id=my.logging.config.id

Thanks much in advance.

That's great food for thought. Greatly appreciate it. A registering appender services sounds like the right approach - I'll have to explore that a bit.

Aside from the medic source code, is there any documentation, blogs, etc. on medic's support of bundle-specific logback configuration? I couldn't find anything except the one page covering the configuration of serviceability and diagnostics.