Tekelija.Allegro.TicketChangeLog

Module handles ticket change log messages, ie. writes log messages to configurable datastore and searches that store for log messages

Configuration

Module config

{
  "TicketChangeLog": {
    "Database": "mongodb",
    "ConnectionString": "mongodb://root:pass@localhost:27017/ticket-log"
  }
}

Parameters:

Name	Type	Default	Description
Database	string	null	Database type: mongodb, mssql, mysql, sqlite
ConnectionString	string	null	Selected database connection string.

Depending of the selected database type, connection string may be something like:

Database	Connection string
mongodb	connection strings should be uris (`mongodb://[<username>:<password>]@<host>[:<port>]/<database>`) inlcuding database name, for example `mongodb://username:password@localhost:27017/ticket-log`
mssql	`server=.\sqlexpress;initial catalog=ticket-log;integrated security=SSPI;`
mysql	`server=localhost;database=ticket-log;username=username;password=password;`
sqlite	`Datasource=.\ticket-log.db;Cache=Shared;`

Message bus config

{
  "MessageBus": {
    "Url": "rabbitmq://localhost",
    "Username": null,
    "Password": null,
    "Endpoint": "<endpoint-name>",
    "MessageRepositoryUri": null
  }
}

Parameters:

Name	Type	Default	Description
Url	string	null	RabbitMQ url (rabbitmq://…)
Username	string	null	RabbitMQ username
Password	string	null	RabbitMQ user password
Endpoint	string	null	RabbitMQ endpoint
MessageRepositoryUri	string	host name	Origin of the call, may have some sense for global call data collection setup