-
Notifications
You must be signed in to change notification settings - Fork 112
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
Enable applications to report what features are being used, what were the states during a request, etc... #3
Comments
Is there any update on this? There is Azure Monitoring and Cost Analysis but I'm not sure that those cover what is requested on this ticket. |
Hello @kevinv53 this is the issue that we are currently designing a solution for. The current line of thought is to have an interface that is internally invoked whenever a flag is evaluated. Exact interface and naming TBD, but something along the lines of the following:
It allows one to implement ITelemetryPublisher and emit/persist feature flag evaluations wherever desired. |
I am excited for the work done in this area, however seeing the I think this was essentially what was asked for in #219 Would you still consider working in that direction, or is |
Can't an implementation of ITelemetryPublisher be made to satsify what you have suggested? |
It can, but that doesn't make a lot of sense to me - as I see it, the TelemetryPublisher is a custom solution duplicating existing framework component. I don't see what's the benefit doing it this way instead of framework-standard. As a bonus, there'd be less public API surface, less maintenance, and more possible optimizations from using framework code. |
From my understanding DiagnosticSource doesn't play as well as we'd like with DI to put us where we want to be for this enhancement. I'm not aware of any patterns to have diagnostic source listeners be DI aware. This makes it a bit difficult to work with in our case given the libraries focus on DI usage. See current proposed usage in Application Insights publisher example:
I appreciate any thoughts you have on the topic. |
It seems there's now It'd be helpful if the framework-based solutions could work more-or-less out of the box, instead of depending on an Azure-focused extension. |
Currently feature management can be used to gate application functionality behind features. An important part of this flow is measuring how often these features are being used, and whether these features are healthy. The feature management interfaces lack the ability to extrapolate data such as what features were accessed during their request and what are their states. This should be added.
The text was updated successfully, but these errors were encountered: