Make elasticsearch/ml_job metricset work for Stack Monitoring without xpack.enabled flag#21043
Conversation
|
Pinging @elastic/stack-monitoring (Stack monitoring) |
|
Pinging @elastic/integrations-services (Team:Services) |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Steps errors
Expand to view the steps failures
|
| Test | Results |
|---|---|
| Failed | 0 |
| Passed | 2312 |
| Skipped | 529 |
| Total | 2841 |
|
When running this, I am seeing this error: |
|
This is now running successfully, thanks @sayden! I'm seeing an issue though - the field in |
|
Ok! Fixed it! Sorry, it's easy that I can miss one of those fields, sometimes they all look the same 😄 |
|
I found something else here too. -> The It looks like the -> |
…csearch/ml-xpack_flag # Conflicts: # metricbeat/docs/fields.asciidoc # metricbeat/module/elasticsearch/_meta/fields.yml # metricbeat/module/elasticsearch/fields.go
…csearch/ml-xpack_flag # Conflicts: # metricbeat/module/elasticsearch/fields.go
ycombinator
left a comment
There was a problem hiding this comment.
Left a comment about a couple of breaking changes and a question about TODOs in field documentation.
| }, | ||
| "ml": { | ||
| "job": { | ||
| "data_counts": { |
There was a problem hiding this comment.
One thing that is confusing me is that in this data.json here, the field path is elasticsearch.ml.job.data_counts.*. But if I look at fields.yml, I'm seeing elasticsearch.ml.job.data.counts.*. Shouldn't the two match up or, failing that, shouldn't there be aliases from all the elasticsearch.ml.job.data_counts.* fields to the corresponding elasticsearch.ml.job.data.counts.* fields so there are breaking changes?
There was a problem hiding this comment.
Yes, you're right. I want a pair of eyes like yours to spot such things 😄
… xpack.enabled flag (elastic#21043)
WIP