Integrate with con terra Applications / server side logging
service.monitor Analytics can be integrated with other con terra products. This is possible due to the same kind of handling and securing of http Requests. Once integration has been accomplished, the following parameters will be logged on client access:
-
basic HTTP request parameters (URL, protocol)
-
basic HTTP response parameters (request duration, HTTP status code)
-
User Agent
-
authentication information
-
client IP
Integrate with con terra security.manager
In order to log information about requests in your security.manager installation, you need to install the shipped GelfWebSecurityProcessor. This processor usually logs via UDP protocol, TCP protocol is also possible.
Steps for installation and configuration
-
Copy the *.jar files located in
[CD-CONTENTS]/analytics/web/service-log/lib
-
to
[security.manager]/webapps/wss/WEB-INF/lib
-
to
[security.manager]/webapps/administration/WEB-INF/lib
-
-
File
[CD-CONTENTS]/analytics/web/service-log/security.manager-<version>/spring-filter-config-administration.xml
:-
to
[security.manager]/webapps/administration/WEB-INF/classes/spring-filter-config.xml
-
-
File
[CD-CONTENTS]/analytics/web/service-log/security.manager-<version>/spring-filter-config-wss.xml
:-
to
[security.manager]/webapps/wss/WEB-INF/classes/spring-filter-config.xml
-
-
Configuration of parameters is done in
[SECURITY_MANAGER_DATA_FOLDER]/application.properties
analytics.gelf.server=myserver.domain.de analytics.gelf.port=12201 analytics.message.src=security.manager analytics.log.enabled=true
-
Please restart your Servlet Container after applying changes.
Integrate with con terra map.apps
In order to log information about requests inside of your map.apps installation, you need to install the shipped GelfWebSecurityFilter
. This processor usually logs via UDP protocol, TCP protocol is also possible.
Steps for installation and configuration
-
Copy the
*.jar
files located in[CD-CONTENTS]/analytics/web/service-log/lib
-
nach
[map.apps]/WEB-INF/lib
-
-
Die Datei
[CD-CONTENTS]/analytics/web/service-log/map.apps-<version>/spring-filter-config.xml
nach[map.apps]/WEB-INF/classes/spring-filter-config.xml
kopieren -
Configuration of parameters is done in
[MAP_APPS_DATA_FOLDER]/application.properties
analytics.gelf.server=myserver.domain.de analytics.gelf.port=12201 analytics.message.src=map.apps analytics.log.enabled=true
-
Please restart your Servlet Container after applying changes.
Overview of integrating map.apps and security.manager
Version | Comment |
---|---|
< 4.15 |
Please update security.manager first |
4.15 - 4.18 |
Procedure as described above |
ab 4.19 |
wss webapp is alread prepared for integration and needs to be configured via application.properties only |
Version | Comment |
---|---|
ab 4.7 |
Procedure as described above |
Integrate with other con terra products
A lot of other con terra products support service.monitor Analytics integration as shown above. Please ask for Support Plus or Consultancy Services for additional Support.
Logging parameters
- useragent
-
Information about the user’s OS and browser
Example:
"user_agent": "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:41.0) Gecko/20100101 Firefox/41.0"
- client_ip
-
Anonymized client IP
Example:
"client_ip": "123.12.12.000"
- request
-
Request parameter information
Example:
"request": { "server_host": "test.remote.host.com", "url_query": "?queryProperty=testvalue", "server_context: "/wss", "referrer": "http://www.mytest.de", "protocol": "https" }
- auth
-
Authentication information
Example:
"auth": { "authenticated": true, "user_id": "userA", "login_time": "2011-17-10 11:17:50", "group_name": "sampleGroup", "roles": [ "admin", "editor" ] }
- response
-
Response parameter information
Example:
"response": { "status": 200 }
- response_time
-
Response time in nano seconds and response time in milli seconds
Example:
"response_time": 12345678, "response_time_ms": 1234.5678