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

Specify include_type_name in HTTP monitoring. #38927

Merged
merged 4 commits into from
Feb 15, 2019

Conversation

jtibshirani
Copy link
Contributor

@jtibshirani jtibshirani commented Feb 14, 2019

In 6.7, include_type_name must be specified in order to avoid deprecation
warnings. Here we make sure to use include_type_name when setting up templates
for the monitoring HTTP exporter.

Addresses #37442.

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features

In 6.7, `include_type_name` must be specified in order to avoid deprecation
warnings. Here we make sure to use `include_type_name` when setting up
templates for the monitoring HTTP exporter.
Copy link
Contributor

@ycombinator ycombinator left a comment

Choose a reason for hiding this comment

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

LGTM.

Map<String, String> parameters = new HashMap<>(
PublishableHttpResource.RESOURCE_VERSION_PARAMETERS);
parameters.put(INCLUDE_TYPE_NAME_PARAMETER, "true");
PARAMETERS = Collections.unmodifiableMap(parameters);
Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Nice, I didn't realize we had that.

Copy link
Contributor

@jakelandis jakelandis left a comment

Choose a reason for hiding this comment

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

LGTM

@jtibshirani
Copy link
Contributor Author

@jakelandis @ycombinator thank you for the reviews! After this merges, it would be good to test HTTP monitoring on 6.7 to make sure there are no deprecation warnings.

@jtibshirani jtibshirani merged commit 10765bd into elastic:6.7 Feb 15, 2019
@jtibshirani jtibshirani deleted the monitoring-types-warnings branch February 15, 2019 04:08
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.

4 participants