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
One issue we've encountered by using Normalization v2 internally is that we have rules that listen on normalized fields that are not interesting to extract into Artifacts, so that we'll be collecting huge numbers of Artifacts that provide no value.
For example, we would normalization network connection protocol, port number among different data sources, however, those values are not interesting and they should not be exacted to the Artifacts.
Desired Change
Add a new configuration for each normalizer that allows you to opt-out of sending a normalized field to the Artifacts Firehose.
The text was updated successfully, but these errors were encountered:
Background
One issue we've encountered by using Normalization v2 internally is that we have rules that listen on normalized fields that are not interesting to extract into Artifacts, so that we'll be collecting huge numbers of Artifacts that provide no value.
For example, we would normalization network connection protocol, port number among different data sources, however, those values are not interesting and they should not be exacted to the Artifacts.
Desired Change
Add a new configuration for each normalizer that allows you to opt-out of sending a normalized field to the Artifacts Firehose.
The text was updated successfully, but these errors were encountered: