-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
Specify include_type_name in HTTP monitoring. #38927
Conversation
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.
c5f652f
to
bb4cfcf
Compare
4d9e4fa
to
25eb787
Compare
There was a problem hiding this 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); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: I think you can use https://github.com/elastic/elasticsearch/blob/master/server/src/main/java/org/elasticsearch/common/collect/MapBuilder.java#L87 to shorten this up abit.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@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. |
In 6.7,
include_type_name
must be specified in order to avoid deprecationwarnings. Here we make sure to use
include_type_name
when setting up templatesfor the monitoring HTTP exporter.
Addresses #37442.