[Geoserver-users] Monitor-hibernate plugin 2.18.x

GeoServer GeoServer User
1

Hi List,
I’m trying to use monitor-hibernate plugin on 2.18.x and I’ve some problems in building it.

before I go too far on that, I was wondering if:

  1. Are some of you successfully using it in production?
  2. can’t see more details on the doc but is it good enough for a production level database?
  3. is the persistence over DB blocking the requests or it’s asynch like the logs?
  4. is it possible to configure the request processor queue (in size?)
  5. if I didn’t a mistake it’s outdated so a pull request is needed, is someone interested working with me on that?

I think that some dependency updates are needed, so I’ve started working on it.

I’ve a ‘working’ branch for that but I still needs to pass tests (and probably we’ve to update javaassist at least for openjdk 11).

  1. what about MIXED mode (disappeared)?

My intention is to persist requests over a database and use that as source for google Analytics to have statistics over area of interests and more in SOFT real time.
Regards,
C.

–

Mr. Carlo Cancellieri
skype: ccancellieri
Twitter: @cancellieric
LinkedIn: http://it.linkedin.com/in/ccancellieri/

2

Hi List,
I’m trying to use monitor-hibernate plugin on 2.18.x and I’ve some problems in building it.

before I go too far on that, I was wondering if:

  1. Are some of you successfully using it in production?

Not that I know of. In my company we use monitoring in audit mode, log on file and
then move the logs to elasticsearch via logstash. Works wonderfully.

  1. can’t see more details on the doc but is it good enough for a production level database?
  1. is the persistence over DB blocking the requests or it’s asynch like the logs?

The way it’s setup, inserts in the database become slower and slower. Eventually they end up locking up
the GeoServer activity as well, because the queue is limited in size (and if it was not, it would lead to OOM).
In my limited experience, it’s basically unusable in production on a busy server (well I guess it could work if the logging table
was periodically flushed).

  1. is it possible to configure the request processor queue (in size?)

Don’t remember

  1. if I didn’t a mistake it’s outdated so a pull request is needed, is someone interested working with me on that?

The module has been dropped down to the community section because no one cared for it anymore. Feel free to take it over.
(personally I won’t be checking the PR contents, but I’m fine merging them if they are not breaking the build).

Cheers
Andrea

···

== 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.