Criticité : 🟠 Moyenne/Élevée (La fonctionnalité offensive ne s'active pas, mais la cause réelle est inconnue)
Occurrences (sur 28 j) : ~25 occurrences (L'erreur la plus fréquente)
Description of the issue
The API frequently logs Failed to send honk_horn for VIN X: Request failed with status code 500. Since we are proxying these commands through the vehicle-command-proxy, the actual reason for the failure (e.g., vehicle asleep, offline, or internal proxy error like context deadline exceeded) is lost because we only log the generic Axios error message.
Expected Behavior
TeslaVehicleCommandService should catch Axios errors and append error.response.data to the log message to provide better observability into why the commands fail.
Logs
[VEHICLE_COMMAND] Failed to send honk_horn for VIN XP7Y...: Request failed with status code 500
Criticité : 🟠 Moyenne/Élevée (La fonctionnalité offensive ne s'active pas, mais la cause réelle est inconnue)
Occurrences (sur 28 j) : ~25 occurrences (L'erreur la plus fréquente)
Description of the issue
The API frequently logs
Failed to send honk_horn for VIN X: Request failed with status code 500. Since we are proxying these commands through thevehicle-command-proxy, the actual reason for the failure (e.g., vehicle asleep, offline, or internal proxy error likecontext deadline exceeded) is lost because we only log the generic Axios error message.Expected Behavior
TeslaVehicleCommandServiceshould catch Axios errors and appenderror.response.datato the log message to provide better observability into why the commands fail.Logs