Hi Andrea,
Your insights are always welcome.
I think you actually told me the same thing at FOSS4G a couple of years
ago when we talked about it, I've just not gotten around to delving into
it; it is somewhere on my todo list... :-)
The downside to that enhancement though is that it requires yet more
setup, configuration, and maintenance. I'm trying to go for simple to
deploy/maintain with this: just point it at your extant logs, tweak the
config file, set up a cron job, start the python web-server and you're done.
Cheers,
Jonathan
On 2018-05-21 11:32, Andrea Aime wrote:
On Mon, May 21, 2018 at 12:11 PM, Jonathan Moules
<[email protected] <mailto:[email protected]>>
wrote:
It basically solves half of the problem the monitoring module
deals with, but with absolutely no performance penalty as it uses
the logs that you're already creating. Its weakness as compared to
the monitoring module is that because it's not integrated into
GeoServer, it can only monitor what gets logged, and it's not
real-time (it's next-day). POST requests don't get logged by
default, but those are usually only WPS and some more complex WFS
requests, so not much is missed.
Hi Jonathan,
you could actually make it work with monitoring in audit mode, which
creates log files with a structure of your choosing, in asynch mode,
so no significant perf penalty either, and
grabbing info also from POST requests (you could, for example turn
them back into GET lookalikes).
That's what we normally do with the audit mode, the only difference is
that we feed the resulting logs into the ELK stack instead, and build
a dashboard that way.
Just thinking out loud :-)
Cheers
Andrea
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.==Ing. Andrea Aime
@geowolfTechnical LeadGeoSolutions S.A.S.Via di Montramito 3/A55054
Massarosa (LU)phone: +39 0584 962313fax: +39 0584 1660272mob: +39
339 8844549http://www.geo-solutions.ithttp://twitter.com/geosolutions_it
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate.
Il loro utilizzo è consentito esclusivamente al destinatario del
messaggio, per le finalità indicate nel messaggio stesso. Qualora
riceviate questo messaggio senza esserne il destinatario, Vi preghiamo
cortesemente di darcene notizia via e-mail e di procedere alla
distruzione del messaggio stesso, cancellandolo dal Vostro sistema.
Conservare il messaggio stesso, divulgarlo anche in parte,
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità
diverse, costituisce comportamento contrario ai principi dettati dal
D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely
for the attention and use of the named addressee(s) and may be
confidential or proprietary in nature or covered by the provisions of
privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New
Data Protection Code).Any use not in accord with its purpose, any
disclosure, reproduction, copying, distribution, or either
dissemination, either whole or partial, is strictly forbidden except
previous formal approval of the named addressee(s). If you are not the
intended recipient, please contact immediately the sender by
telephone, fax or e-mail and delete the information in this message
that has been received in error. The sender does not give any warranty
or accept liability as the content, accuracy or completeness of sent
messages and accepts no responsibility for changes made after they
were sent or for other risks which arise as a result of e-mail
transmission, viruses, etc.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
