Chapter 1. Overview

Tigase Audit Log component is an implementation of Audit Log pattern functionality to log important events in a system such as:

By default log entries are stored in auditlog file in form of a JSON objects.

It is possible to enable searchable storage which will use MySQL table to store auditlog entries and will make them accessible for administrators via AdminUI. For more information about searchable storage please check Configuration of searchable repository

Following informations will be stored for logged event (if data was available for particular event):

Name of propertyAdditional info

from

packet source

to

packet destination

type

event type - possible values are:

  • auth.success
  • auth.failure
  • auth.disconnected
  • presence
  • subscribe
  • message
  • vcard
  • jingle

when

timestamp of an event

allowed

true/false value which informs if this log entry was expected

serverName

name of cluster node which generated this event

errorCode

error code

errorMessage

error message

callId

sid of a Jingle call or a thread of a message

internalError

true if error was caused by internal error

errorCondition

added additionally which contains also info about policyName

stanzaId

id of logged stanza

connection

id of user connection if available - points to particular connection from particular device