You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Steps to Reproduce: This bug is intermittent. To attempt to recreate, start the Elastic stack with elastic-package stack up --version 8.0.0-SNAPSHOT -v. Log in to Kibana at localhost:5601. Create an Elastic Synthetics policy, and wait for Uptime data to be indexed by heartbeat. Return to Fleet and edit the policy. Occasionally, editing the policy will create the following error in elastic agent's heartbeat logs, and data will stop being indexed.
13:43:14.904
elastic_agent.heartbeat
[elastic_agent.heartbeat][error] Error creating runner from config: monitor ID 90639f1a-094a-45cb-9fdc-62982ee67e82 is configured for multiple monitors! IDs must be unique values.
13:43:14.904
elastic_agent.heartbeat
[elastic_agent.heartbeat][error] 1 error: Error creating runner from config: monitor ID 90639f1a-094a-45cb-9fdc-62982ee67e82 is configured for multiple monitors! IDs must be unique values.
The text was updated successfully, but these errors were encountered:
Fixeselastic#28518 most likely, it's one I haven't personally been able to
repro. This makes the runner list synchronous, thus preventing rapid
adds/removes from creating simultaneously live plugins of the same type.
There's definitely ways to do this more concurrently, but that sort of
optimization/complexity isn't warranted here. Heartbeat can tear down
monitors near instantaneously.
For confirmed bugs, please report:
elastic-package stack up --version 8.0.0-SNAPSHOT -v
. Log in to Kibana atlocalhost:5601
. Create an Elastic Synthetics policy, and wait for Uptime data to be indexed by heartbeat. Return to Fleet and edit the policy. Occasionally, editing the policy will create the following error in elastic agent's heartbeat logs, and data will stop being indexed.The text was updated successfully, but these errors were encountered: