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

Remove or refactor the performance counter API #434

Closed
tusmester opened this Issue Jul 31, 2018 · 0 comments

Comments

Projects
None yet
2 participants
@tusmester
Copy link
Member

tusmester commented Jul 31, 2018

The CounterManager class is built on the .net performance counter API (but it does not expose it on its public API). That api is available in netstandard, but we should consider removing this feature and encourage users to use sensenet tracing instead (?).

Option1

Remove the CounterManager api. This is the more expensive solution.

  • documentation: how and when to use SnTrace for performance monitoring?
  • create a new issue (#480) for a new counter API

Option2

Use the PerformanceCounter package and leave the feature as it is.

@kultsar kultsar added this to the Sprint 170 milestone Oct 24, 2018

@kultsar kultsar modified the milestones: Sprint 170, Sprint 171 Nov 5, 2018

@kultsar kultsar closed this Nov 7, 2018

@tusmester tusmester removed the discussion label Jan 22, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment