Add output of instance configuration at startup
Summary
At the moment, the configuration with which the instance was started is only partially present in the logs, and the one that is displayed is highly fragmented.
>>>>> start_discover()
2023-01-09 13:28:09.914 [8] main/103/interactive I> Tarantool 2.10.4-19-g9912156ed
2023-01-09 13:28:09.914 [8] main/103/interactive I> log level 5
2023-01-09 13:28:09.914 [8] main/103/interactive I> wal/engine cleanup is paused
2023-01-09 13:28:09.914 [8] main/103/interactive I> mapping 33554432 bytes for memtx tuple arena...
2023-01-09 13:28:09.914 [8] main/103/interactive I> Actual slab_alloc_factor calculated on the basis of desired slab_alloc_factor = 1.044274
2023-01-09 13:28:09.914 [8] main/103/interactive I> mapping 134217728 bytes for vinyl tuple arena...
2023-01-09 13:28:09.916 [8] main/103/interactive I> update replication_synchro_quorum = 1
2023-01-09 13:28:09.916 [8] main/103/interactive I> instance uuid 12e2dc6c-b0d8-47ed-9b79-471b46272127
2023-01-09 13:28:09.916 [8] main/103/interactive I> initializing an empty data directory
2023-01-09 13:28:09.922 [8] main/103/interactive I> assigned id 1 to replica 12e2dc6c-b0d8-47ed-9b79-471b46272127
2023-01-09 13:28:09.922 [8] main/103/interactive I> update replication_synchro_quorum = 1
2023-01-09 13:28:09.922 [8] main/103/interactive I> cluster uuid fcfd41da-9278-4c80-8615-307951e67af6
2023-01-09 13:28:09.922 [8] snapshot/101/main I> saving snapshot `./00000000000000000000.snap.inprogress'
2023-01-09 13:28:09.923 [8] snapshot/101/main I> done
2023-01-09 13:28:09.923 [8] main/103/interactive I> RAFT: fencing enabled
2023-01-09 13:28:09.923 [8] main/103/interactive I> ready to accept requests
2023-01-09 13:28:09.923 [8] main/105/gc I> wal/engine cleanup is resumed
2023-01-09 13:28:09.923 [8] main/103/interactive I> set 'log_level' configuration option to 5
2023-01-09 13:28:09.923 [8] main/103/interactive I> set 'feedback_enabled' configuration option to false
2023-01-09 13:28:09.923 [8] main/103/interactive I> set 'log_format' configuration option to "plain"
2023-01-09 13:28:09.923 [8] main/103/interactive I> set 'memtx_memory' configuration option to 33554432
2023-01-09 13:28:09.923 [8] main/103/interactive I> set 'replication_connect_quorum' configuration option to 32
2023-01-09 13:28:09.923 [8] main/103/interactive I> set 'replication' configuration option to []
2023-01-09 13:28:09.923 [8] main/106/checkpoint_daemon I> scheduled next checkpoint for Mon Jan 9 14:51:32 2023
2023-01-09 13:28:09.929 [8] main/103/interactive I> tx_binary: bound to 10.85.0.155:3301
2023-01-09 13:28:09.929 [8] main/103/interactive I> set 'listen' configuration option to "10.85.0.155:3301"
Possible solution
If it is possible to add a detailed output of the entire configuration at once at any of the logging levels.
>>>>> start_picodata()
2023-01-09 13:28:09.914 [8] main/103/interactive I> 'data_dir': "/opt/picodata"
2023-01-09 13:28:09.914 [8] main/103/interactive I> 'instance-id': "storage-1"
2023-01-09 13:28:09.914 [8] main/103/interactive I> 'listen': "10.85.0.155:3301"
2023-01-09 13:28:09.914 [8] main/103/interactive I> 'advertise_uri': "storage-1.interconnect.svc.cluster.local"
2023-01-09 13:28:09.914 [8] main/103/interactive I> 'reer_uri': "router-0.interconnect.svc.cluster.local"
2023-01-09 13:28:09.914 [8] main/103/interactive I> 'cluster-id': "my-cluster"
2023-01-09 13:28:09.914 [8] main/103/interactive I> 'init-replication-factor': 2
2023-01-09 13:28:09.914 [8] main/103/interactive I> 'log_level': "info"
...