sibislogger feature - for "warnings", don't reopen Github issue

[shippy]

sibispy doesn't have a great general approach to reporting things that aren't straight-up errors. If any sibislogger message occurs, a Github issue is opened or re-opened. Any resolution that doesn't make the error go away requires a special_cases entry, which typically requires privileged access to our systems.

One way to create warnings would be to have the Github poster behave differently for them - i.e. only open new Github issues, but don't reopen any. This would help shelve "unresolved" cases without requiring a config entry - the RA just closes the issue if the warning is a false positive, and it doesn't recur.

[jimklo]

Actually what might be better is if we can hash the general cause of the warning. It’s more than likely multiple issues of the same type all lead to the same cause.

Then have sibislogger only comment on an existing issue (reopening if closed) adding instance specific details. This way only a handful of issues are opened instead of thousands and related problems automatically get grouped together.

Alternatively a logging service might be more useful which could also buffer and collate similar errors together.

[shippy]

That's useful for "bug" issues, where there's one underlying problem. Most of the raised issues are "data" issues, though, where the resolution is subject-specific and you want to track each one individually.