I also want to know when join requests fail to process because:
Device with matching EUI does not exist on the server.
Device with matching EUI exists but app_key is incorrect.
In a past version of chirpstack I was able to create a shell script to scrape the log files and use telegraf to dump this info into influxdb but the messages have changed in the latest version so that doesn’t work anymore.
What is the best method to keep track of these joins over all gateways over time?
While technically possible, the uplink from the chirpstack-gateway-bridge for device join requests just has the raw payload which needs to be translated from base64 to hex and then get the eui from those bytes which is more complicated than I think it needs to be.