Application logging

WEBAPP:

Description

Log format

/var/log/veridiumid/opa/opa.out

OPA logs

json

/var/log/veridiumid/tomcat/catalina.out

tomcat logs, where websec/shibboleth/adservice/dmz applications are deployed; this are general logs, to see that tomcat has started and applications deployed

%d{yyyy-MMM-dd HH:mm:ss a} [%t] %level %logger{36} %msg%n

/var/log/veridiumid/tomcat/bops.log

These logs are the main application logs, containing the websec logs.

%d{yyyy-MMM-dd HH:mm:ss a} [%t] %level %logger{36} %msg%n

/var/log/veridiumid/tomcat/ldap.log

These logs contains the interaction logs with LDAP service.

%d{yyyy-MMM-dd HH:mm:ss a} [%t] %level %logger{36} %msg%n

/var/log/veridiumid/fido/fido.log

The fido logs containing application logs related to fido usage.

%d{yyyy-MMM-dd HH:mm:ss a} [%t] %level %logger{36} %msg%n

/var/log/veridiumid/notifications/notifications.log

In this log, can be found the information about the notification process, containing the part of mail and sms sending messages.

%d{yyyy-MMM-dd HH:mm:ss a} [%t] %level %logger{36} %msg%n

/var/log/veridiumid/statistics/dashboard-sessions-local.log

Dashboards logs by the applications used by process dashboard-sessions-local. In case in websecadmin are not presented statistics, this is the log where the user should look.

%d{yyyy-MMM-dd HH:mm:ss a} [%t] %level %logger{36} %msg%n

/var/log/veridiumid/statistics/dashboard-sessions-global.log

Dashboards logs by the applications used by process dashboard-sessions-global. In case in websecadmin are not presented statistics, this is the log where the user should look.

%d{yyyy-MMM-dd HH:mm:ss a} [%t] %level %logger{36} %msg%n

/var/log/veridiumid/statistics/account-sessions.log

Dashboards logs by the applications used by process account-sessions. In case in websecadmin are not presented statistics, this is the log where the user should look.

%d{yyyy-MMM-dd HH:mm:ss a} [%t] %level %logger{36} %msg%n

/var/log/veridiumid/statistics/account-bioengines.log

Dashboards logs by the applications used by processaccount-bioengines. In case in websecadmin are not presented statistics, this is the log where the user should look.

%d{yyyy-MMM-dd HH:mm:ss a} [%t] %level %logger{36} %msg%n

/var/log/veridiumid/statistics/auth-sessions-local.log

Dashboards logs by the applications used by process auth-sessions-local. In case in websecadmin are not presented statistics, this is the log where the user should look.

%d{yyyy-MMM-dd HH:mm:ss a} [%t] %level %logger{36} %msg%n

/var/log/veridiumid/statistics/auth-sessions-global.log

Dashboards logs by the applications used by process auth-sessions-global. In case in websecadmin are not presented statistics, this is the log where the user should look.

%d{yyyy-MMM-dd HH:mm:ss a} [%t] %level %logger{36} %msg%n

/var/log/veridiumid/selfservice/selfservice.log

This is the self service application log.

%d{yyyy-MMM-dd HH:mm:ss a} [%t] %level %logger{36} %msg%n

/var/log/veridiumid/websecadmin/websecadmin.log

This is the websecadmin application log, where are kept the logs for user interaction with websec admin application.

%d{yyyy-MMM-dd HH:mm:ss a} [%t] %level %logger{36} %msg%n

/var/log/veridiumid/freeradius/freeradius.log

Freeradius log contains the information about freeradius application.

%d{yyyy-MMM-dd HH:mm:ss a} %msg%n

/var/log/veridiumid/shibboleth-idp/idp-warn.log

This is the main log for shibboleth process.

%d{yyyy-MMM-dd HH:mm:ss a} [%t] %level %logger{36} %msg%n

/var/log/veridiumid/websecadmin/deprovisioning.log

This is the deprovisioning process log, where can be seen action taken by this process.

%d{yyyy-MMM-dd HH:mm:ss a} [%t] %level %logger{36} %msg%n

/var/log/veridiumid/haproxy/haproxy.log

Haproxy application log contains the acces logs of all services.

according to documentation, tcp log and http log for haproxy
log-format "%ci:%cp [%t] %ft %b/%s %Tw/%Tc/%Tt %B %ts %ac/%fc/%bc/%sc/%rc %sq/%bq"
log-format "%ci:%cp [%tr] %ft %b/%s %TR/%Tw/%Tc/%Tr/%Ta %ST %B %CC %CS %tsc %ac/%fc/%bc/%sc/%rc %sq/%bq %hr %hs %{+Q}r"

PERSISTENCE:

/var/log/veridiumid/cassandra/debug.log

This is the cassandra log, where can be seen the database logs. 

%d{yyyy-MMM-dd HH:mm:ss a} [%t] %level %logger{36} %msg%n

/var/log/veridiumid/cassandra/backup.log

This log contains information about backup activities, that are running in crontab periodically.

%d{yyyy-MMM-dd HH:mm:ss a} %level %msg%n

/var/log/veridiumid/cassandra/maintenance.log

This log contains information about maintenance activities, that are running in crontab periodically.

%d{yyyy-MMM-dd HH:mm:ss a} %level %msg%n

/var/log/veridiumid/kafka/server.log

This is the main kafka log.

[%d] %p %m (%c)%n

/var/log/veridiumid/zookeeper/zookeeper.log

This is the main zookeeper log.

%d{ISO8601} [myid:%X{myid}] - %-5p [%t:%C{1}@%L] - %m%n

/var/log/veridiumid/data-retention/data-retention.log

Data retention process log.

%d{yyyy-MMM-dd HH:mm:ss a} [%t] %level %logger{36} %msg%n

Access log:

/var/log/veridiumid/tomcat/shib_localhost_access_log..2023-05-30.log

Access log for shibboleth, including all called API, response and duration.

SHIBBOLETH %h %{X-Forwarded-For}i %l %u %t "%r" %s %b %D %S %I DN=%{X-SSL-Client-DN}i CN=%{X-SSL-Client-CN}i

/var/log/veridiumid/tomcat/dmz_localhost_access_log..2023-05-30.log

Access log for dmz, including all called API, response and duration.

DMZ %h %{X-Forwarded-For}i %l %u %t "%r" %s %b %D %S %I DN=%{X-SSL-Client-DN}i CN=%{X-SSL-Client-CN}i

/var/log/veridiumid/tomcat/localhost_access_log..2023-05-30.txt

Access log for websec and ADService including all called API, response and duration.

WEBAPP %h %{X-Forwarded-For}i %l %u %t "%r" %s %b %D %S %I DN=%{X-SSL-Client-DN}i CN=%{X-SSL-Client-CN}i

/var/log/veridiumid/websecadmin/access_log.2023-05-30.log

Access log for websecadmin including all called API, response and duration.

%h %l %u %t \"%r\" %s %b %D

/var/log/veridiumid/selfservice/access_log.2023-05-30.log

Access log for selfservice including all called API, response and duration.

%h %l %u %t "%r" %s %b %D

/var/log/veridiumid/fido/access_log.2023-05-30.log

Access log for fido including all called API, response and duration.

%h %l %u %t "%r" %s %b %D

Audit logs:

/opt/veridiumid/websecadmin/logs/events.log

Events logs for accessing websecadmin

%d{yyyy-MMM-dd HH:mm:ss a} [%t] %level %logger{36} %msg%n

/opt/veridiumid/tomcat/logs/events.log

Events logs for user authentications

%d{yyyy-MMM-dd HH:mm:ss a} [%t] %level %logger{36} %msg%n