Dear List,
The monitor extension has received an improvement where users can now disable un-necessary post processors from configuration file. Complete details can be found at https://osgeo-org.atlassian.net/browse/GEOS-9436.
An early backport is humbly requested.
regards,
Imran
I.R
minor change, quite isolated.
+0
Ing. Simone Giannecchini
@simogeo
Founder/Director
GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928
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.
Not sure I understand, in this context what is a post processor?
–
Jody Garnett
+0 looks like an isolated change, without any impact unless the user explicit activates the functionality
@Jody, this description help me understood what’s going on (from the doc):
Ignore Post Processors
----------------------
The monitor passes request information through post processors which enrich the request
information with DNS lookup, Location using IP database etc. It is possible to disable
these post processors if some enrichments are not required with ignorePostProcessors
property of the monitor.properties file.
This parameter takes comma separated names of known post processors.
The valid values are reverseDNS,geoIp,layerNameNormalizer
On Wed, 2020-01-08 at 08:05 -0800, Jody Garnett wrote:
Not sure I understand, in this context what is a post processor?
On Wed, Jan 8, 2020 at 3:19 AM Imran Rajjad <rajjad@anonymised.com> wrote:
Dear List,
The monitor extension has received an improvement where users can now disable un-necessary post processors from configuration file. Complete details can be found at https://osgeo-org.atlassian.net/browse/GEOS-9436.
An early backport is humbly requested.
regards,
Imran_______________________________________________ Geoserver-devel mailing list [Geoserver-devel@anonymised.comsts.sourceforge.net](mailto:Geoserver-devel@lists.sourceforge.net) [https://lists.sourceforge.net/lists/listinfo/geoserver-devel](https://lists.sourceforge.net/lists/listinfo/geoserver-devel)
--
Regards,
Nuno Oliveira
==
GeoServer Professional Services from the
experts!
Visit http://goo.gl/it488V for more information.
==
Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer
GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
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.
Hi Jody,
The monitoring extensions passed incoming OWS requests through a series of processes to yield information, which is used to create a monitoring record which is later used in stats calculation. These processes are basically implementations of a single interface. Currently, with the monitoring extension enabled, each OWS requests is processed by all implementations for post processing an OWS requests, To enrich the monitoring record, the post processors cross match information between OWS request and external info sources (e.g GeoIP information) or Reverse DNS lookups etc. There might be times when these enrichments are not desired, so this improvements allows user to disable the post processing through configuration file, as pointed out by Nuno. For backward compatibility, all processors are enabled by default, until specifically mentioned with correct name in properties file.
regards,
Imran
I.R
Thank you,
Nuno explained also: +1
–
Jody Garnett