# Metricbeat mysql 8.2.3 fleet integration failing

**URL:** <https://discuss.elastic.co/t/metricbeat-mysql-8-2-3-fleet-integration-failing/307306>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [June 15, 2022, 4:15pm UTC](https://discuss.elastic.co/t/metricbeat-mysql-8-2-3-fleet-integration-failing/307306 "2022-06-15T16:15:13Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![rbos](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@rbos](https://discuss.elastic.co/u/rbos)\
**Post date:** [June 15, 2022, 4:15pm UTC](https://discuss.elastic.co/t/metricbeat-mysql-8-2-3-fleet-integration-failing/307306/1 "2022-06-15T16:15:13Z")

</div>

On all my hosts that have upgraded to elastic-agent 8.2.3 (with the RHEL packages), the "mysql" integration is failing with:

`{"log.level":"error","@timestamp":"2022-06-15T09:01:06.421-0700","log.origin":{"file.name":"log/reporter.go","file.line":36},"message":"2022-06-15T09:01:06-07:00 - message: Application: metricbeat--8.2.3[7b2f7d07-75ed-4341-9cb3-f749a2b0a7b0]: State changed to FAILED: 1 error occurred:\n\t* 1 error: Error creating runner from config: missing required field accessing 'hosts'\n\n - type: 'ERROR' - sub_type: 'FAILED'","ecs.version":"1.6.0"}`

and then getting stuck in a restart loop.

in the logs. I've tried reinstalling elastic-agent, re-enrolling them. I had some brief success when I cloned the policy without mysql, then re-added it, but the error came back after restarting elastic-agent on my test server.

I thought it was maybe a once-off but it started happening on a second and third server.

---

<div class="post-metadata">

**Author:** ![Andrea\_Spacca](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrea_spacca/32/76976_2.png) [@Andrea\_Spacca](https://discuss.elastic.co/u/Andrea_Spacca)\
**Post date:** [June 16, 2022, 2:42am UTC](https://discuss.elastic.co/t/metricbeat-mysql-8-2-3-fleet-integration-failing/307306/2 "2022-06-16T02:42:20Z")

</div>

hello @rbos ,

what version of the mysql integration have you installed?

---

<div class="post-metadata">

**Author:** ![rbos](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@rbos](https://discuss.elastic.co/u/rbos)\
**Post date:** [June 16, 2022, 3:01am UTC](https://discuss.elastic.co/t/metricbeat-mysql-8-2-3-fleet-integration-failing/307306/3 "2022-06-16T03:01:02Z")

</div>

It appears to be v1.2.1. I just re-added it, fresh, to my test group, and the error started appearing again. [So it looks like the most current one.](https://docs.elastic.co/en/integrations/mysql#changelog)

---

<div class="post-metadata">

**Author:** ![lalits](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lalits/32/107097_2.png) [@lalits](https://discuss.elastic.co/u/lalits)\
**Post date:** [June 16, 2022, 3:18am UTC](https://discuss.elastic.co/t/metricbeat-mysql-8-2-3-fleet-integration-failing/307306/4 "2022-06-16T03:18:16Z")

</div>

What elastic agent version was running fine earlier?

---

<div class="post-metadata">

**Author:** ![rbos](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@rbos](https://discuss.elastic.co/u/rbos)\
**Post date:** [June 16, 2022, 3:20am UTC](https://discuss.elastic.co/t/metricbeat-mysql-8-2-3-fleet-integration-failing/307306/5 "2022-06-16T03:20:20Z")

</div>

3.2.2. Installed perhaps last week.

---

<div class="post-metadata">

**Author:** ![lalits](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lalits/32/107097_2.png) [@lalits](https://discuss.elastic.co/u/lalits)\
**Post date:** [June 16, 2022, 3:57am UTC](https://discuss.elastic.co/t/metricbeat-mysql-8-2-3-fleet-integration-failing/307306/6 "2022-06-16T03:57:28Z")

</div>

@rbos,

Can you confirm if you have enabled "performance metrics". Please disable it and re-run.

We have filed an issue: [MYSQL: performance data\_stream configs not passed · Issue #3514 · elastic/integrations · GitHub](https://github.com/elastic/integrations/issues/3514)

---

<div class="post-metadata">

**Author:** ![rbos](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@rbos](https://discuss.elastic.co/u/rbos)\
**Post date:** [June 16, 2022, 1:48pm UTC](https://discuss.elastic.co/t/metricbeat-mysql-8-2-3-fleet-integration-failing/307306/7 "2022-06-16T13:48:26Z")

</div>

Confirmed, that seems to stop the restart loop.

edit: I probably don't actually need the performance metrics anyway. Thanks, this can be considered fixed for me. Good luck fixing the underlying problem!

---

<div class="post-metadata">

**Author:** ![lalits](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lalits/32/107097_2.png) [@lalits](https://discuss.elastic.co/u/lalits)\
**Post date:** [June 18, 2022, 5:15am UTC](https://discuss.elastic.co/t/metricbeat-mysql-8-2-3-fleet-integration-failing/307306/8 "2022-06-18T05:15:16Z")

</div>

Glad you are able to proceed for now.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 16, 2022, 7:16am UTC](https://discuss.elastic.co/t/metricbeat-mysql-8-2-3-fleet-integration-failing/307306/9 "2022-07-16T07:16:13Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
