You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have noticed that initializing the LoggingDB with the default APPID and CLIENTID results in poor performance in certain moments, maybe the timber instances allocated for these APPID/CLIENTID are not sufficient anymore?
In order to make it easier for the user to set his own credentials / inform him he may need to register his client as specified in the wiki, can we
check if APPID and CLIENTID are specified,
if they are not specified, try and read this info from a configuration.properties file in the same folder as the script (as one can already do with the java CLI)
if this fails, print a warning "using the default appid and clientid can result in poor performance...."
The text was updated successfully, but these errors were encountered:
I have noticed that initializing the LoggingDB with the default APPID and CLIENTID results in poor performance in certain moments, maybe the timber instances allocated for these APPID/CLIENTID are not sufficient anymore?
In order to make it easier for the user to set his own credentials / inform him he may need to register his client as specified in the wiki, can we
The text was updated successfully, but these errors were encountered: