I recently upgraded metricbeat on our kubernetes environment with mixed os platform and realised our windows metricbeat build was broken with error 'The system can not find the path specified'. upon looking deeper into metricbeat installation i noticed earlier metricbeat.cmd file used to be stored at C:\Program Files\Elastic\Beats\ and metricbeat.exe executable at C:\Program Files\Elastic\Beats\\metricbeat
however now with version 8.13, metricbeat.cmd file and metricbeat.exe is stored at same location C:\Program Files\Elastic\Beats\\metricbeat. but the problem is metricbeat.cmd has not been updated to reflect this change and still refers to metricbeat.exe and other files in metricbeat folder instead of looking at current directory.
Hi,
I recently upgraded metricbeat on our kubernetes environment with mixed os platform and realised our windows metricbeat build was broken with error 'The system can not find the path specified'. upon looking deeper into metricbeat installation i noticed earlier metricbeat.cmd file used to be stored at C:\Program Files\Elastic\Beats\ and metricbeat.exe executable at C:\Program Files\Elastic\Beats\\metricbeat
however now with version 8.13, metricbeat.cmd file and metricbeat.exe is stored at same location C:\Program Files\Elastic\Beats\\metricbeat . but the problem is metricbeat.cmd has not been updated to reflect this change and still refers to metricbeat.exe and other files in metricbeat folder instead of looking at current directory.
here is contents of metricbeat.cmd:
For confirmed bugs, please report: