It is probably a code bug, if you have a logging profile with _LOGGING.properties or _LOGGING.yaml I would like it to be listed. I only wrote a custom xml parser (to modify the geoserver log filename during loading) so the other file formats will need to have an explicit filename. -- Jody Garnett
On Tue, 30 Aug 2022 at 10:28, Bingen Galartza Iparragirre < bingen.galar...@magnet.coop> wrote: > Hello, > > The documentation[1] states that the logging profile filenames located in > the* GEOSERVER_DATA_DIR/logs* folder must match the **_LOGGING.** > expression. But in practice we realized that they must actually end with > *_LOGGING.xml* in order to appear in the settings page. Looking at the > source-code we found two references [2][3] to the profile filename checking > (although we might be missing more). As it can be seen in the code, one is > checking just for the presence of *_LOGGING*, and the other if the name > ends with* _LOGGING.xml*. > > So at this point we are not sure if it's a documentation or code bug. > Would be happy to open a Jira issue after knowing your opinion on this. > > [1] > https://docs.geoserver.org/latest/en/user/configuration/logging.html#custom-logging-profiles > > [2] > https://github.com/geoserver/geoserver/blob/fff7f21864727c238f72206ace54a0ae2bef532c/src/web/core/src/main/java/org/geoserver/web/admin/GlobalSettingsPage.java#L276 > > [3] > https://github.com/geoserver/geoserver/blob/cc0e4cc922db1684f1fc9fb4a7ff0e871e179599/src/main/src/main/java/org/geoserver/logging/LoggingUtilsDelegate.java#L581 > > Thank you > -- > *BINGEN GALARTZA IPARRAGIRRE* > > > > > magnet.coop > Santa Marina 3, Oñati (20560) > i...@magnet.coop > *www.magnet.coop <http://www.magnet.coop>* > > *This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this > communication in error, please notify the sender immediately and delete it. > If you are not the intended recipient, you are expressly prohibited from > reading, copying, distributing, disseminating or, in any other way, using > any of the information without the Magnet consent. Please note that > Internet e-mail guarantees neither the confidentiality nor the proper > receipt of the message sent, so that Magnet shall not be liable for any > damages caused. As its integrity cannot be secured on the Internet, the > Magnet liability cannot be triggered for the message content. Although the > sender endeavors to maintain a computer virus-free network, the sender does > not warrant that this transmission is virus-free and will not be liable for > any damages resulting from any virus transmitted.* > _______________________________________________ > Geoserver-users mailing list > > Please make sure you read the following two resources before posting to > this list: > - Earning your support instead of buying it, but Ian Turton: > http://www.ianturton.com/talks/foss4g.html#/ > - The GeoServer user list posting guidelines: > http://geoserver.org/comm/userlist-guidelines.html > > If you want to request a feature or an improvement, also see this: > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > > > Geoserver-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-users >
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
