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
At the moment logging is configured to write asctime, levelname and message.
Would it be possible to add in an option in the configuration file to enable additional parameters to be logged, such as the LAT/LONG that's displayed on the CLI friendly log?
This isn't anything of great benefit right now, but would be a nice to have to potentially visualise in another tool, with the free tier of aprs.fi only allowing you to view received beacons over the last 24 hours.
The text was updated successfully, but these errors were encountered:
@Nodeswitch I can certainly manage that. Additionally, what do you think about logging right to a CSV type format for easy import into a spreadsheet or database system?
At the moment logging is configured to write asctime, levelname and message.
Would it be possible to add in an option in the configuration file to enable additional parameters to be logged, such as the LAT/LONG that's displayed on the CLI friendly log?
This isn't anything of great benefit right now, but would be a nice to have to potentially visualise in another tool, with the free tier of aprs.fi only allowing you to view received beacons over the last 24 hours.
The text was updated successfully, but these errors were encountered: