Skip to content
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

Add Drop Strings Processor #3763

Conversation

KarstenSchnitter
Copy link
Contributor

This processor will drop all metrics with string values. This is helpful in
cases where the complete set of metrics is unknown or unsure but non-numerical
values should be avoided, e.g. for compliance reasons.

Required for all PRs:

  • Signed CLA.
  • Associated README.md updated.
  • Has appropriate unit tests.

This processor will drop all metrics with string values. This is helpful in
cases where the complete set of metrics is unknown or unsure but non numerical
values should be avoided.

Signed-off-by: Karsten Schnitter <[email protected]>
@sjwang90
Copy link
Contributor

Is this something that can now be addressed with processors.starlark?

@KarstenSchnitter
Copy link
Contributor Author

KarstenSchnitter commented Nov 18, 2020

I agree, that with the right script, this issue can be addressed with the starlark processor plugin. The user has to develop and maintain that script though. Maybe this case can be included in the testdata? I am not so sure, how to test for the type of the metric since starlark is a dynamic language. This is necessary to drop fields based on their type.

@srebhan srebhan self-assigned this Nov 18, 2020
@srebhan srebhan mentioned this pull request Nov 19, 2020
3 tasks
@ssoroka
Copy link
Contributor

ssoroka commented Nov 19, 2020

I think I'm going to close this in favor of #8438, which is more flexible. Otherwise we might end up with drop_x plugins for all available types.

@ssoroka ssoroka closed this Nov 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants