initial policy project proposal#3569
Conversation
|
@jsuereth @dashpole @jackshirazi I've updated based on your feedback. PTAL! 🙇 |
| - **Experimental policies** for the initial scope: **sampling, filtering, and | ||
| scoped transformations**. Additional transform types for things like | ||
| datapoints and other policy types are deferred and added iteratively. | ||
| - **Applied-policy reporting.** Scope and formalize how a component reports |
There was a problem hiding this comment.
How do we know which policies were applied by the collector if the collector process crashed before it could even report those metrics?
There was a problem hiding this comment.
General health and availability of the collector is already something that can be established by existing means (e.g. prometheus up metric, k8s liveness probes, or other forms of uptime monitoring). This will allow operators to diagnose issues with a policy that isn't applied (e.g. because it is invalid) or issues delivering policies, or will allow operators to tell how long it takes between when a policy is defined by the user, and when a policy is actually being enforced.
7 participants
This is the proposal to establish a project around the recently merged OTEP. The goal is to create alpha components, a specification, and more implementations and recommendations.