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
It should treat softwareVersion as a minimum to report on, so that any later versions are also reported on. It's currently a strict equality check.
The script should take a configuration file for the various softwareName + softwareVersions it should be reporting on. This would enable developers of uploading softwareNames to PR a bump to the version.
This would remove any need to implement something to keep up with the latest versions of the uploading softwares, which are not always released on GitHub (so can't just use the 'latest release' URL redirect trick).
Allowing developers to check 'their' output
It should have a mode where it writes a timestamp-named file to a per-softwareName directory with all matching, unexcluded lines (any PII elided). The idea is to then publicise the top-level of this and developers of uploading software then have the responsibility to check the contents. It would likely be run daily as the easiest way to only process new log lines is to run on the just copied file during log rotation.
This would remove any need to implement something to keep up with the latest versions of the uploading softwares, which are not always released on GitHub (so can't just use the 'latest release' URL redirect trick).
It should have a mode where it writes a timestamp-named file to a per-softwareName directory with all matching, unexcluded lines (any PII elided). The idea is to then publicise the top-level of this and developers of uploading software then have the responsibility to check the contents. It would likely be run daily as the easiest way to only process new log lines is to run on the just copied file during log rotation.
So, e.g. there would be https://eddn.edcd.io/reports/by-time/EDDiscovery/eddn-errors-2021-01-12T07:07:34Z.txt with the
by-time
directory, and the per-softwareName ones, indexable.If we have some issue that's throwing an exception, e.g. #164 , we need to be alerted to that.
The text was updated successfully, but these errors were encountered: