Skip to content

Updating Metricbeat stack modules to ECS#10350

Merged
ycombinator merged 22 commits intoelastic:masterfrom
ycombinator:mb-stack-ecs
Jan 31, 2019
Merged

Updating Metricbeat stack modules to ECS#10350
ycombinator merged 22 commits intoelastic:masterfrom
ycombinator:mb-stack-ecs

Conversation

@ycombinator
Copy link
Copy Markdown
Contributor

@ycombinator ycombinator commented Jan 26, 2019

This PR updates a few fields in the Elastic stack modules in Metricbeat, viz. elasticsearch, logstash, and kibana to their ECS names and types.

Based on discussions happening in #10218, but only scoped to Elastic stack modules.

@elasticmachine
Copy link
Copy Markdown
Contributor

Pinging @elastic/stack-monitoring

@ycombinator ycombinator added review and removed in progress Pull request is currently in progress. labels Jan 26, 2019
@ycombinator ycombinator requested review from ruflin and webmat January 26, 2019 15:54
@ycombinator ycombinator changed the title [WIP] Updating Metricbeat stack modules to ECS Updating Metricbeat stack modules to ECS Jan 26, 2019
Copy link
Copy Markdown
Contributor

@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.

You also need to update the ecs-migration.yml file.

@ruflin ruflin mentioned this pull request Jan 28, 2019
@ycombinator
Copy link
Copy Markdown
Contributor Author

@ruflin This is ready for another review pass. I addressed feedback from your previous review and left a couple of questions as well. Thanks!

Copy link
Copy Markdown
Contributor

@webmat webmat left a comment

Choose a reason for hiding this comment

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

Looking pretty good. Only need to resolve on the PID inconsistency. Also noticed a few service.version that haven't been migrated yet.

Once these are settled, this LGTM

@ycombinator
Copy link
Copy Markdown
Contributor Author

@webmat @ruflin Addressed latest round of feedback. This is ready for your 👀 again, when you get a chance. Thanks!

@ycombinator
Copy link
Copy Markdown
Contributor Author

jenkins, test this

Copy link
Copy Markdown
Contributor

@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.

Overall LGTM. One minor comment.

I think we need to figure out what we do with the hostname fields. What we could do is get this PR in without the hostname fields and figure it out as a follow up.

@ycombinator
Copy link
Copy Markdown
Contributor Author

@ruflin Other than your second thoughts comments that require third thoughts from @webmat 😉 I've addressed all your other feedback.

@webmat
Copy link
Copy Markdown
Contributor

webmat commented Jan 29, 2019

@ruflin @ycombinator I think for both transport_address and hostname we could have them under service.*. This would neatly solve the problem of monitoring services from the outside vs locally.

@ycombinator
Copy link
Copy Markdown
Contributor Author

ycombinator commented Jan 29, 2019

@webmat said:

I think for both transport_address and hostname we could have them under service.*. This would neatly solve the problem of monitoring services from the outside vs locally.

Just to clarify, you're saying that:

@webmat
Copy link
Copy Markdown
Contributor

webmat commented Jan 29, 2019

Mostly yes, but I'll clarify one last thing 😆

I think kibana.stats.transport_address should be migrated to service.address

@ycombinator
Copy link
Copy Markdown
Contributor Author

@webmat Took another shot at the language per your recommendations. Ready for your 👀 again, when you get a chance. Thanks!

Copy link
Copy Markdown
Contributor

@webmat webmat left a comment

Choose a reason for hiding this comment

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

Great! Thanks @ycombinator

LGTM

@webmat
Copy link
Copy Markdown
Contributor

webmat commented Jan 30, 2019

Of course I had to click too fast and not make this "Approved" 😆

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