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
#5680 introduces a DSL for filtering logs, and based on prior discussions we want to consider a similar approach for metric transforms/filters too. Before committing to this approach and this library, we'd like to do a deeper evaluation:
overall performance impact of evaluating DSL at runtime
comparison with other DSL approaches
can we handle filter for resource && inst lib && signal without evaluating resource multiple times
Thanks @bogdandrutu for the detailed suggestion. Please add any other evaluation criteria that are on your mind.
The text was updated successfully, but these errors were encountered:
My apologies for not working on this issue. However, in light of @anuraaga's work on a generic transform processor (design doc, WIP implementation), I believe this evaluation is no longer necessary.
#5680 introduces a DSL for filtering logs, and based on prior discussions we want to consider a similar approach for metric transforms/filters too. Before committing to this approach and this library, we'd like to do a deeper evaluation:
filter for resource && inst lib && signal
without evaluating resource multiple timesThanks @bogdandrutu for the detailed suggestion. Please add any other evaluation criteria that are on your mind.
The text was updated successfully, but these errors were encountered: