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
| ✅ |[Logging](#logging)| Integrate with popular logging packages. |
108
108
| ✅ |[Domains](#domains)| Logically bind clients with providers. |
109
109
| ✅ |[Eventing](#eventing)| React to state changes in the provider or flag management system. |
110
+
| ✅ |[Tracking](#tracking)| Associate user actions with feature flag evaluations. |
110
111
| ✅ |[Shutdown](#shutdown)| Gracefully clean up a provider during application shutdown. |
111
112
| ✅ |[Transaction Context Propagation](#transaction-context-propagation)| Set a specific [evaluation context](https://openfeature.dev/docs/reference/concepts/evaluation-context) for a transaction (e.g. an HTTP request or a thread) |
112
113
| ✅ |[Extending](#extending)| Extend OpenFeature with custom providers and hooks. |
The [tracking API](https://openfeature.dev/specification/sections/tracking/) allows you to use OpenFeature abstractions and objects to associate user actions with feature flag evaluations.
192
+
This is essential for robust experimentation powered by feature flags.
193
+
For example, a flag enhancing the appearance of a UI component might drive user engagement to a new feature; to test this hypothesis, telemetry collected by a [hook](#hooks) or [provider](#providers) can be associated with telemetry reported in the client's `track` function.
194
+
195
+
```python
196
+
from openfeature.track import TrackingEventDetails
0 commit comments