Skip to main content
Version: 8.2505.x.x RR

NevisProxy trace groups

The nevisProxy trace groups adjust the verbosity of the messages recorded in the log file regarding specific nevisProxy filters and servlets. For an overview of the various log levels, see Log level below.

BC.Tracer.DebugProfile.NPAuthFilter​

Type: integer
Usage Constraint: 0-10

Traces the functioning of and defines the log level for the AuthenticationFilter.

BC.Tracer.DebugProfile.NPParamVldFlt​

Type: integer
Usage Constraint: 0-10

Traces the functioning of and defines the log level for the ParameterValidationFilter.

BC.Tracer.DebugProfile.NPHdrVldFlt​

Type: integer
Usage Constraint: 0-10

Traces the functioning of and defines the log level for the HeaderValidationFilter.

BC.Tracer.DebugProfile.NPSessionFlt​

Type: integer
Usage Constraint: 0-10

Traces the functioning of and defines the log level for the SessionManagementFilter.

BC.Tracer.DebugProfile.NPCountryIpFlt​

Type: integer
Usage Constraint: 0-10

Traces the functioning of and defines the log level for the CountryIpFilter.

BC.Tracer.DebugProfile.NPDynCfgFlt​

Type: integer
Usage Constraint: 0-10

Traces the functioning of and defines the log level for the DynamicConfigFilter.

BC.Tracer.DebugProfile.NPXmlFilter​

Type: integer
Usage Constraint: 0-10

Traces the functioning of and defines the log level for the XMLFilter.

BC.Tracer.DebugProfile.WSInspFlt​

Type: integer
Usage Constraint: 0-10

Traces the functioning of WebSocketInspectionFilter, and defines the log level for the WebSocketInspectionFilter.

BC.Tracer.DebugProfile.NPMemLeakFlt​

Type: integer
Usage Constraint: 0-10

Traces the functioning of and defines the log level for the MemoryLeakFilter.

BC.Tracer.DebugProfile.NPReaperOp​

Type: integer
Usage Constraint: 0-10

Traces the functioning of and defines the log level for the SessionManagementFilter. If set to INFO ("6"), this trace group will print out statistical information of the local store or the MySQL store used by a SessionManagementFilter.

BC.Tracer.DebugProfile.NPLocalSessStr​

Type: integer
Usage Constraint: 0-10

Traces the functioning of and defines the log level for the LocalSessionStoreServlet.

BC.Tracer.DebugProfile.NPMySQLSessSrv​

Type: integer
Usage Constraint: 0-10

Traces the functioning of and defines the log level for the MySQLSessionStoreServlet: On level INFO ("6"), this trace group traces the statistics about timed-out, removed and zombie sessions. On level DEBUG_HIGH ("9"), the trace group logs all SQL requests regarding the MySQL/MariaDB remote session store used by a SessionManagementFilter.

BC.Tracer.DebugProfile.NPReqObsFlt​

Type: integer
Usage Constraint: 0-10

Traces the functioning of and defines the log level for the RequestObserverFilter.

BC.Tracer.DebugProfile.NPMultiLevelStr​

Type: integer
Usage Constraint: 0-10

Traces the functioning of and defines the log level for the MultiLevelSessionStoreServlet. On log level INFO ("6"), this trace group traces the number of waiting sessions and the delay (in seconds) to the configured BackupServlet, in a regular interval. TheBackupServletis one of the parameters of theMultiLevelSessionStoreServlet. It defines the servlet used to back up the session information. The trace interval is configured with the parameterPeriodicityin the filenavajo.xml.If one of the configured thresholds is reached, a NOTICE message is traced (instead of an INFO). The thresholds are specified in the parameters BackupThreads.DelayThreshold and BackupThreads.QueueLengthThreshold of the MultiLevelSessionStoreServlet.".

BC.Tracer.DebugProfile.NPBackendSrv​

Type: integer
Usage Constraint: 0-10

Traces the functioning of and defines the log level for the BackendConnectorServlet.

BC.Tracer.DebugProfile.NPLoadBalance​

Type: integer
Usage Constraint: 0-10

Traces the functioning of and defines the log level for the LoadBalancerServlet.

BC.Tracer.DebugProfile.NPPerfMeter​

Type: integer
Usage Constraint: 0-10

Valid for all filters: If the RequestFlag NEEDS_TIME_METER is set, an INFO message of the time spent in this filter will be traced. If the RequestFlag NEEDS_TIME_METER is not set, an INFO message of the time spent in a filter will only be traced, if a request takes longer than the configured in the property BC.Tracer.DebugProfile.NPPerfMeter.InfoTimeout.

BC.Tracer.DebugProfile.NPPerfMeter.InfoTimeout​

Type: integer
Unit: milliseconds

Valid for all filters, except for those filters that have the RequestFlag NEEDS_TIME_METER configured. If the time spent in a specific filter is equal or greater than the timeout configured in this property, the system will trace an INFO message on the trace group NPPerfMeter. The INFO message contains the filter name and the time spent. Setting this property helps you check which filters are slow in case you have some performance issues. Make sure to also set the trace level of NPPerfMeter to "INFO". If, for example, the filter is called MyFilter, the message will look like:

2020 11 25 11:27:18.620 4.4.0 NPPerfMete 47288.140477112874752.00b8b8-16063000381708837-175fef17434 6-INFO : (MyFilter) time spent: 299 msecs

BC.Tracer.DebugProfile.NPPerfMeter.DetailLevel​

Type: integer
Usage Constraint: 0-10

Configures how detailed the timing related log entries will be. When 3 or larger value is set, an additional instructions per milliseconds (IPMS) metric is traced. Instruction calculating requires /proc/sys/kernel/perf_event_paranoid <= 1 and when ran inside docker, an additional PERFMON capability needs to be enabled and the perf_event_open syscall has to be whitelisted in seccomp.