Hi Vera and Kris, the monitoring database module has been kicked down to "community module" status, meaning it's not part of releases anymore and has no module maintainer.
The way data was stored in a database was problematic too, with one single table with primary key, which was making inserts slower and slower (due to checking of PK uniqueness at every insert), to the point that after some amount of requests (hundreds of thousands) the monitoring inserts were taking more time than the request itself. The hibernate version used was also old. Long story short, in order to resume this module we'd need: - A maintainer, someone that cares for the module - Some changes to make insert sustainable (basically, make it so that it works in absence of a primary key, or some other approach to avoid tables to grow too large) - A hibernate upgrade, possibly to a recent version If you have ability and time to do the above, it would be very much appreciated. Otherwise, monitoring "core" is still supported and used normally in "audit" mode, logging to a text file, which is normally processed asynchronously by some external utility of your choice to gather statistics. A common choice is the ELK stack, Logstash to load the requests logs into ElastichSearch, and a Kibana dashboard to display the results Cheers Andrea On Sat, Dec 22, 2018 at 4:33 PM Vera Green <[email protected]> wrote: > I have no advice but am looking forward to anyone's reply as I would like > to set this up as well. > Vera > > On Fri, Dec 21, 2018, 2:26 PM Kris Johnson <[email protected] wrote: > >> Hello, >> >> I am attempting to setup and configure the monitoring extension for >> Geoserver 2.13.3 so that requests will be recorded in a postgresql database. >> I have followed the instructions provided here: >> https://docs.geoserver.org/stable/en/user/community/monitor-hibernate/db.html#monitor-db >> And two tables have been created in the database ("request" and >> "request_resources"). However, despite multiple new requests showing up on >> the [host]..../geoserver/rest/monitor/requests page, I have zero records >> in either table. >> >> Is there something I'm missing here? Thank you in advance for your help. >> >> -- >> Kris Johnson >> GIS Instructor >> Department of Geography, Urban and Environmental Sustainability Studies >> University of Minnesota - Duluth >> 324 Cina Hall >> Duluth, MN 55812 >> 218-726-6226 >> >> _______________________________________________ >> 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 >> >> >> [email protected] >> 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 > > > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users > -- Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- *Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.*
_______________________________________________ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
