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

Updating elasticsearch/ccr metricset with ES ccr_stats API changes #9179

Conversation

ycombinator
Copy link
Contributor

@ycombinator ycombinator commented Nov 20, 2018

Resolves elastic/kibana#25778.

The ES CCR API changed a little before the 6.5.0 FF and we didn't catch these changes 😞. This PR updates the CCR metricset code to work with the new ES CCR API response structure.

Testing this PR

  1. Setup CCR: https://www.elastic.co/guide/en/elastic-stack-overview/current/ccr-getting-started.html
  2. Checkout this PR and make Metricbeat: cd metricbeat; make
  3. Enable the elasticsearch module: ./metricbeat modules enable elasticsearch
  4. Edit modules.d/elasticsearch.yml and make sure the ccr metricset is enabled and xpack.enabled: true is set.
  5. Start Metricbeat: ./metricbeat -e
  6. After about 10-20 seconds, check that Metricbeat indexed the correct document of type = ccr_stats into .monitoring-es-mb-6-*.

Copy link
Contributor

@chrisronline chrisronline left a comment

Choose a reason for hiding this comment

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

Functionality LGTM! I'm able to index monitoring documents that the UI expects!

@ycombinator
Copy link
Contributor Author

jenkins, test this

Copy link
Member

@ruflin ruflin left a comment

Choose a reason for hiding this comment

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

LGTM from a code perspective. Didn't test it locally.

Sounds like this needs a changelog entry?

@@ -1,30 +1,30 @@
{
"@timestamp": "2017-10-12T08:05:34.853Z",
"beat": {
"agent": {
Copy link
Member

Choose a reason for hiding this comment

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

keep in mind for the backport ;-)

@ycombinator ycombinator force-pushed the metricbeat-elasticsearch-ccr-update-schema branch from 3c99e8d to 72e0a76 Compare November 21, 2018 16:20
@ycombinator ycombinator merged commit 3a9d920 into elastic:master Nov 21, 2018
@ycombinator ycombinator removed the needs_backport PR is waiting to be backported to other branches. label Nov 21, 2018
ycombinator added a commit to ycombinator/beats that referenced this pull request Nov 22, 2018
…lastic#9179)

Resolves elastic/kibana#25778.

The ES CCR API changed a little before the 6.5.0 FF and we didn't catch these changes 😞. This PR updates the CCR metricset code to work with the new ES CCR API response structure.

## Testing this PR
1. Setup CCR: https://www.elastic.co/guide/en/elastic-stack-overview/current/ccr-getting-started.html
2. Checkout this PR and `make` Metricbeat: `cd metricbeat; make`
3. Enable the `elasticsearch` module: `./metricbeat modules enable elasticsearch`
4. Edit `modules.d/elasticsearch.yml` and make sure the `ccr` metricset is enabled and `xpack.enabled: true` is set.
5. Start Metricbeat: `./metricbeat -e`
6. After about 10-20 seconds, check that Metricbeat indexed the correct document of `type` = `ccr_stats` into `.monitoring-es-mb-6-*`.
ycombinator added a commit that referenced this pull request Nov 26, 2018
…S ccr_stats API changes (#9201)

* Updating elasticsearch/ccr metricset with ES ccr_stats API changes (#9179)

Resolves elastic/kibana#25778.

The ES CCR API changed a little before the 6.5.0 FF and we didn't catch these changes 😞. This PR updates the CCR metricset code to work with the new ES CCR API response structure.

## Testing this PR
1. Setup CCR: https://www.elastic.co/guide/en/elastic-stack-overview/current/ccr-getting-started.html
2. Checkout this PR and `make` Metricbeat: `cd metricbeat; make`
3. Enable the `elasticsearch` module: `./metricbeat modules enable elasticsearch`
4. Edit `modules.d/elasticsearch.yml` and make sure the `ccr` metricset is enabled and `xpack.enabled: true` is set.
5. Start Metricbeat: `./metricbeat -e`
6. After about 10-20 seconds, check that Metricbeat indexed the correct document of `type` = `ccr_stats` into `.monitoring-es-mb-6-*`.

* Renaming field for 6.x
@ycombinator ycombinator deleted the metricbeat-elasticsearch-ccr-update-schema branch December 25, 2019 11:13
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.

3 participants