Closed kent-williams closed 1 year ago
Hmm interesting, I did not expect invalid requests to be logged there.
My first thought was this is an easy fix .. I just need to filter on the request status .. but apparently that is not available in the request log :disappointed:
The only available fields are service
, method
and metadata
.. and metadata only contains response headers starting with (x-log-)
I think this an oversight on the chirpstack side. I will create an issue/pr for that on the chirpstack repo
For now I will add some code to handle these errors more graceful
I have found the service to crash if any invalid API requests are made. For instance, the below crash was after attempting device creation via the Chirpstack API with a missing
dev_eui
. It seems like we might need some better data validation to avoid this.