Jody Garnett
2017-06-23 00:34:50 UTC
I am having fun using geoserver this week (I know that never happens that
developers get to use the thing they work on).
One of the experiments I have been doing it starting up geoserver with an
empty data directory and configuring it via the rest api. One "glitch" in
this work flow is configuring logging.
When I first start up geoserver logs are sent to catalina.out and are
available in tomcat/logs directory. The
GEOSERVER_DATA_DIR/logs/geoserver.log file is created but empty.
When I use the UI to change logging from default to production, the log4j
configuration files are unpacked into GEOSERVER_DATA_DIR/logs and the
GEOSERVER_DATA_DIR/logs/geoserver.og file starts being used.
I am happy to report a bug / feature request, but would like to ask if I am
missing something obvious first.
Do we need a geoserver/rest/settings/logging endpoint to configure these
settings (or is it already too late after first launch).
--
Jody Garnett
developers get to use the thing they work on).
One of the experiments I have been doing it starting up geoserver with an
empty data directory and configuring it via the rest api. One "glitch" in
this work flow is configuring logging.
When I first start up geoserver logs are sent to catalina.out and are
available in tomcat/logs directory. The
GEOSERVER_DATA_DIR/logs/geoserver.log file is created but empty.
When I use the UI to change logging from default to production, the log4j
configuration files are unpacked into GEOSERVER_DATA_DIR/logs and the
GEOSERVER_DATA_DIR/logs/geoserver.og file starts being used.
I am happy to report a bug / feature request, but would like to ask if I am
missing something obvious first.
Do we need a geoserver/rest/settings/logging endpoint to configure these
settings (or is it already too late after first launch).
--
Jody Garnett