Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error reporting script improvements #167

Open
3 tasks
Athanasius opened this issue Jan 12, 2022 · 0 comments
Open
3 tasks

Error reporting script improvements #167

Athanasius opened this issue Jan 12, 2022 · 0 comments

Comments

@Athanasius
Copy link
Contributor

  • Keeping up with softwareVersions
  1. 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.
  2. 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.

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.


  • Reporting of any other ERROR lines not pertaining to specific software.

If we have some issue that's throwing an exception, e.g. #164 , we need to be alerted to that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant