Other important loggers

Other important loggers are useful in troubleshooting Content Integration. Along with spotting warnings and errors, these loggers provide information that is useful from a functional point of view.

The following table lists the other important loggers:

Client applications - If root logger level is set to INFO level, the following lines tells you the number of client applications, and which client applications Content Integration can identify:
```
SupportedClientApplications: Found {1} supported client applications.
SupportedClientApplications: Registered {Offer} as supported client application.
```

CORS - If root logger is set to INFO level, the following lines can provide information about Content Integration’s support for Cross Origin Resource Sharing:

RegexCorsConfig: CORS: Enabling CORS for {hcl.com} & its subdomains. Allowed HTTP methods - {[GET, POST]}, allowed headers - {[*]}
RegexCorsConfig: CORS: Allowed origins set to {[http(s)?://([^\.]+\.)*hcl.com(:[0-9]+)?]}

Platform configuration - Content repositories - Setting the root logger level to INFO tells us about the content repositories that are identified by Content Integration Framework.

PlatformConfigurationCategoryResolver: Platform configuration: Reading list of entries for path {Affinium|Offer|partitions|partition1|Content Integration|dataSources}...
PlatformCmsConfigurationReader: Platform configuration: Imported settings for {AEM#119[partition1]}
PlatformCmsConfigurationReader: Platform configuration: Imported settings for {WCM#119[partition1]}
PlatformCmsConfigurationReader: Platform configuration: Imported settings for {Bing#119[partition1]}

Service meta information files - The following lines are also logged at INFO level to tell how many service meta information files have been identified by Content Integration Framework:


c.h.u.s.c.s.PluginServicesYamlConfigReader: Scanning & parsing service configuration files.
c.h.u.s.c.s.PluginServicesYamlConfigReader: Seeking file at {<ASSET_PICKER_HOME>\conf\plugin-services.yml}.
c.h.u.s.c.s.PluginServicesYamlConfigReader: Found service config file at {<ASSET_PICKER_HOME>/conf/plugin-services.yml} 
c.h.u.s.c.s.PluginServicesYamlConfigReader: Parsing service configuration file (YAML): {<ASSET_PICKER_HOME>/conf/plugin-services.yml}...
c.h.u.s.c.s.PluginServicesYamlConfigReader: Seeking file at {<ASSET_PICKER_HOME>\conf\custom-plugin-services.yml}.
c.h.u.s.c.s.PluginServicesYamlConfigReader: {1} service declaration(s) found for {COM} - {[COM:get-object-schema]}
c.h.u.s.c.s.PluginServicesYamlConfigReader: {12} service declaration(s) found for {WCM} - {[WCM:item-details, WCM:simple-search, WCM:content-list, WCM:logon-service, WCM:list-contents, WCM:library-list, WCM:get-content-details, WCM:folder-list, WCM:get-object-schema, WCM:list-folders, WCM:library-by-id, WCM:resource-loader]}
c.h.u.s.c.s.PluginServicesYamlConfigReader: {31} service declaration(s) found for {Deliver} - {[Deliver:update-folder, Deliver:simple-search, Deliver:list-by-ids, Deliver:zip-file-upload, Deliver:delete-content, Deliver:move-folder, Deliver:create-content, Deliver:list-folders, Deliver:zip-upload-template-unknown, Deliver:move-content, Deliver:list-sub-folders, Deliver:download-content-variant, Deliver:download-file-attachment, Deliver:get-user-entitlements, Deliver:list-top-folders, Deliver:update-dynamic-content, Deliver:create-folder, Deliver:find-libraries-by-name, Deliver:resource-loader, Deliver:zip-upload-content, Deliver:adopt-dynamic-content, Deliver:get-folder, Deliver:create-dynamic-content, Deliver:list-contents, Deliver:get-content-details, Deliver:patch-content, Deliver:delete-folder, Deliver:get-library, Deliver:update-content, Deliver:get-library-file, Deliver:adopt-content]}
c.h.u.s.c.s.PluginServicesYamlConfigReader: {1} service declaration(s) found for {Azure} - {[Azure:get-cognitive-analysis]}
c.h.u.s.c.s.PluginServicesYamlConfigReader: {1} service declaration(s) found for {DX-CORE} - {[DX-CORE:logon-service]}
c.h.u.s.c.s.PluginServicesYamlConfigReader: {7} service declaration(s) found for {DX} - {[DX:simple-search, DX:list-contents, DX:get-content-details, DX:rendition-details, DX:get-object-schema, DX:list-folders, DX:resource-loader]}
c.h.u.s.c.s.PluginServicesYamlConfigReader: {7} service declaration(s) found for {Commerce} - {[Commerce:simple-search, Commerce:list-contents, Commerce:get-content-details, Commerce:get-search-query-suggestions, Commerce:list-content-categories, Commerce:get-object-schema, Commerce:list-folders]}
c.h.u.s.c.s.PluginServicesYamlConfigReader: {7} service declaration(s) found for {AEM} - {[AEM:simple-search, AEM:list-contents, AEM:get-content-details, AEM:get-object-schema, AEM:get-content-fragment-model, AEM:list-folders, AEM:sample-inbound-service]}
c.h.u.s.c.s.PluginServicesYamlConfigReader: {2} service declaration(s) found for {Bing} - {[Bing:simple-search, Bing:get-content-details]}

Authentication protocols - The following lines, logged at INFO level, confirms the authentication protocol is identified for the given content repository:
```
AssetPickerRestTemplate: Setting up {BASIC} authentication for {Offer[partition1].WCM:simple-search} service...
```
Platform configuration cache invalidation and service re-initializations - All the Platform configurations for Content Integration are cached during application startup. These configurations are refreshed after certain interval (every 30 mins by default unless configured to use some other interval). The following logger is produced at INFO level, whenever configuration refresh begins:
```
INFO  [scheduling-1] c.h.u.s.c.s.ServiceBootstrapper: Re-initializing services...
```
Similarly, the following lines are generated at INFO level whenever it is over:
```
INFO  [scheduling-1] c.h.u.s.c.s.ServiceBootstrapper: Finished service initializations.
INFO  [scheduling-1] c.h.u.s.c.s.ServiceBootstrapper: Re-initialization completed in 3692 milliseconds. YAML read time: 15 milliseconds, DB Read Time: 3608 milliseconds, Service initialization time: 68 milliseconds
```