-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[NEW-FEATURE] Add feat to monitor the connector performance #197
Milestone
Comments
/cib |
Branch 197-_NEW-FEATURE_Add_feat_to_monitor_the_connector_performance created! |
PTKu
added a commit
that referenced
this issue
Aug 2, 2023
* Create draft PR for #197 * add logging for perfomance monitoring. # SetLoggerConfiguration - connector has now SetLoggerConfiguration method to provide an option to set up customized logger, that will override the default logger of the connector e.g. ~~~ new LoggerConfiguration() .WriteTo .Console() .WriteTo .File($"connector{GetType()}.log", outputTemplate: "{Timestamp:yyyy-MMM-dd HH:mm:ss} [{Level}] {Message}{NewLine}{Exception}", fileSizeLimitBytes: 100000) .MinimumLevel.Information() .CreateLogger(); ~~~ # Verbose and debug logging (webapi connector) - debug log when reading and writing occurs infoming about number of processed items - verbose will provide detailed information about symbols being accessed and polling counts. ## Removes the OnInitialized - RCC removes call of OnInitialized method when Presentation type is set, due to reduntant method call that affects the polling counter. * fixes previous merge * wip improvements to polling * wip - polling and perf improvements * improvements to polling and + documenation additions * doc additions and clean up * nuget packages consolidation * mend --------- Co-authored-by: PTKu <PTKu@users.noreply.github.com> Co-authored-by: Peter Kurhajec <61538034+PTKu@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: