Skip to content

Remove device_name/DeviceName specificity#314

Merged
olivielpeau merged 3 commits intomasterfrom
olivielpeau/remove-device-name-specificity
Jun 19, 2017
Merged

Remove device_name/DeviceName specificity#314
olivielpeau merged 3 commits intomasterfrom
olivielpeau/remove-device-name-specificity

Conversation

@olivielpeau
Copy link
Copy Markdown
Member

What does this PR do?

  • Treat device_name as any other tag instead of treating it as a specific field
  • Make AgentCheck support the device_name parameter on metric submission methods, but log a deprecation warning

Motivation

  • Clean up aggregator
  • Support python checks that use device_name

Additional Notes

I can queue some work to remove all uses of device_name from our integrations-core checks, I can do that once we're 100% sure that this change won't make the backend create duplicate contexts.

Should be replaced by a "standard" `device:` tag. This change shouldn't
make a difference in the backend, I'll make sure of that though.

* `AgentCheck` supports `device_name` as a parameter to the metric
submission methods for backwards-compatibility, but we should stop
supporting it at some point.
* Remove all traces of `DeviceName` field in aggregator
Copy link
Copy Markdown
Member

@hush-hush hush-hush left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you also remove the DeviceName from sketch_series.go and in serializer_test.go function: TestMarshalJSONSketchSeries ?

Except that it LGTM.

@olivielpeau
Copy link
Copy Markdown
Member Author

Thanks @hush-hush, I had missed that. I've addressed your comment 👍

@olivielpeau olivielpeau merged commit d94742e into master Jun 19, 2017
@olivielpeau olivielpeau deleted the olivielpeau/remove-device-name-specificity branch June 19, 2017 15:45
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.

2 participants