Closed carsonip closed 1 month ago
Completed local testing on all https://github.com/elastic/beats/pull/40127, https://github.com/elastic/elasticsearch/pull/110568, and https://github.com/elastic/integrations/pull/10414. Note that both https://github.com/elastic/elasticsearch/pull/110568 and https://github.com/elastic/integrations/pull/10414 require https://github.com/elastic/beats/pull/40127 to have output.elasticsearch.*
metrics parsed.
.monitoring-beats-7-*
).monitoring-beats-8-mb
)metricbeat-*
)metrics-elastic_agent-apm_server-*
)While the Python script in https://github.com/elastic/apm-server/pull/13638 generates the correct mapping for all the above use cases, this approach is not very maintainable. Ideally, having dynamic: true
like metricbeat standalone enables apm-server monitoring fields to be mapped dynamically and will require minimal maintenance. However, since EA agent mapping already has TSDB enabled, disabling TSDB now and enabling dynamic mapping sounds like a step back.
Tested on 8.15 BC2, (UPDATE) followup testing with 8.15 BC3:
[x] APM server self-monitoring: tested with ESS elasticsearch, ~❌ the backport PR was not merged. It is merged now, and will require testing again in BC3.~ Tested with updated BC and is working as expected.
[x] APM server stack monitoring: tested on ESS, ~❌ the backport PR was not merged. It is merged now, and will require testing again in BC3.~ Tested with updated BC and is working as expected.
[x] Metricbeat without x-pack, tested locally with apm-server 008b12a7e9929ce00e01040e67e83cf19c0b7de7 and beats 417ac43a6193bdf26da490d41532b2f2d5bc3f70
[x] EA integration tested with locally running EA using elastic-agent-package 475d247d16a94af14b75d991a8da3d63d68e8042. ~❌ While the test succeeded, I had to manually upgrade EA integration as the version bundled in Kibana is still older (v1.20.0
) whereas the latest version is v2.0.1
- since this is not related to the current issue, marking this point as done.~ Confirmed that with BC3 the latest version v2.0.1
of elastic-agent integration is bundled.
Moved all remaining tasks to #13731 . Closing this issue as the bug of missing metrics is now fixed.
Discovered by #13244
EA managed apm-server is only shipping a subset of apm-server monitoring metrics. This limits observability of EA managed apm-server. The problem is spread over the following use cases:
state
,stats
.monitoring-beats-7-*
state
,stats
.monitoring-beats-8-mb
state
,stats
metricbeat-*
stats
onlymetrics-elastic_agent.apm_server.*
(see code)POST kbn:/api/fleet/epm/packages/elastic_agent
Unknowns:
apm-server:5066/stats
will not be pure addition. Not sure if dropping a field mapping will be problematic.