Nice, I will look at that for inspiration.

Quick comment: your REST API use `PUT /logger` to add a logger, and `POST 
/logger` to update an exosting logger.  While that of course works it's a bit 
unusual because normally POST is used to create new items, and PUT is used to 
update existing items.


</nk>

---


Norbert Kiesel
Systems Architect | Engineering
MetricStream
2600 E. Bayshore Road | Palo Alto, CA - 94303
+1-650-620-2954 | [email protected] | www.metricstream.com


________________________________
From: logback-user <[email protected]> on behalf of Martin Todorov 
<[email protected]>
Sent: Thursday, March 31, 2016 12:00 PM
To: logback users list
Subject: Re: [logback-user] produce configuration file from current 
configuration?



Hi Norbert,

We recently put together the following project:
- https://github.com/carlspring/logback-configuration
[https://avatars1.githubusercontent.com/u/1436265?v=3&s=400]<https://github.com/carlspring/logback-configuration>

carlspring/logback-configuration<https://github.com/carlspring/logback-configuration>
github.com
Contribute to logback-configuration development by creating an account on 
GitHub.




It has a simple REST API and a Spring-based service layer. It's quite easy to 
set up. It has some straight-forward test cases which you can have a look at in 
order to figure out how things work.
I haven't yet pushed it Maven Central, but if it looks like something you might 
want to use, let me know and I'll release a version 1.0.

Let me know what you think!
Kind regards,

Martin Todorov




On Thu, Mar 31, 2016 at 6:49 PM, Norbert Kiesel 
<[email protected]<mailto:[email protected]>> wrote:

Hi,


we finally switched from a home-grown logging system to slf4j/logback and are 
overall happy.  However, the old solution (which was much  more limited) 
offered a web GUI for setting the root log level.  We could of course implement 
that using the logback API.  However, this will of not be reflected in our 
logback.xml.  I'm also worried that any other change in that file will simply 
reset the log level given that we use the `scanPeriod` option.


Is there a way to convert a current logback configuration back into an XML (or 
Groovy) configuration file?


</nk>

---


Norbert Kiesel
Systems Architect | Engineering
MetricStream
2600 E. Bayshore Road | Palo Alto, CA - 94303
+1-650-620-2954<tel:%2B1-650-620-2954> | 
[email protected]<mailto:[email protected]> | 
www.metricstream.com<http://www.metricstream.com>

Confidentiality Notice:This email and any files transmitted with it are 
confidential and intended solely for the use of the individual or entity to 
whom they are addressed. This message contains confidential information and is 
intended only for the individual named. If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail. Please notify the 
sender immediately by e-mail if you have received this e-mail by mistake and 
delete this e-mail from your system. If you are not the intended recipient you 
are notified that disclosing, copying, distributing or taking any action in 
reliance on the contents of this information is strictly prohibited

_______________________________________________
logback-user mailing list
[email protected]<mailto:[email protected]>
http://mailman.qos.ch/mailman/listinfo/logback-user

_______________________________________________
logback-user mailing list
[email protected]
http://mailman.qos.ch/mailman/listinfo/logback-user

Reply via email to