Log parameters, appenders, and files

Default log files directory: ./instances/<instance-name>/logs/

Appender	Parameters	IAM Modules
Appender	Parameters	Loginapp	Adminapp	Transaction Approval	Service Container	API Policy Service
`STRUCTURED-FILE`	`iam.log.structured-file.*`	`loginapp-structured.log`	`adminapp-structured.log`	`transaction-approval-structured.log`	`servicecontainerapp-structured.log`	`api-policy-service-structured.log`
`STRUCTURED-STDOUT`	`iam.log.structured-stdout.*`	(`/dev/stdout`)
-	`iam.log.elasticsearch`	(Elasticsearch)
`MAIN`	`iam.log.main.*`	`loginapp.log`	`adminapp.log`	`transaction-approval.log`	`servicecontainerapp.log`	`api-policy-service.log`
`CONSOLE`	-	(`/dev/stdout`)
`PARSABLE`	-	`loginapp-parsable.log` ¹	`adminapp-parsable.log` ¹	`transaction-approval-parsable.log` ¹	`servicecontainerapp-parsable.log` ¹	`api-policy-service-parsable.log` ¹
`IAM-USER-TRAIL`	-	`medusa-usertrail.log` ¹^,²
`IAM-AUDIT`	-	`medusa-audit.log`
Web Server:
-	`iam.web-server.log.*`	`web-server.log.*`
-	`iam.web-server.access-log.*`	`access.log`

1		The Adminapp log viewer uses this log file. Changing the format or deleting lines in these files will break the log viewer. The log file format may change without prior notice.
2		User trail logging into the `medusa-usertrail.log` file is outdated. New Airlock IAM installations of 8.0 and later log into a database by default. This also applies to upgraded installations where the configuration migration was successful.