data_transfer_log_level only supports LOG_NOTICE and LOG_DEBUG

[alanking]

If the configuration value string is anything other than "LOG_NOTICE", it will remain at the default level of LOG_DEBUG.

Here's the default value:

irods_capability_storage_tiering/include/irods/private/storage_tiering/configuration.hpp

Lines 26 to 27 in 8d0872f

	const std::string data_transfer_log_level_key{"data_transfer_log_level"};
	int data_transfer_log_level_value{LOG_DEBUG};

And here's where we are overriding the value in configuration:

irods_capability_storage_tiering/src/configuration.cpp

Lines 78 to 83 in 8d0872f

	if(plugin_spec_cfg.find(data_transfer_log_level_key) != plugin_spec_cfg.end()) {
	const std::string& val = plugin_spec_cfg.at(data_transfer_log_level_key).get_ref<const std::string&>();
	if("LOG_NOTICE" == val) {
	data_transfer_log_level_value = LOG_NOTICE;
	}
	}

We are using the LOG_<level> semantics of the legacy iRODS logging. We might want to change these strings to be like our new logging system (i.e. "trace", "debug", "info", "warn", "error"). In fact, we might want to consider creating a log category for this plugin...

[korydraughn]

A dedicated log category sounds great. That'll be a great help to admins and devs needing to debug the plugin.