Diagnostics Plugin issueshttps://gitlab.nic.cz/turris/reforis/reforis-diagnostics/-/issues2020-11-27T10:33:53+01:00https://gitlab.nic.cz/turris/reforis/reforis-diagnostics/-/issues/8Does it make sense to display diagnostic names?2020-11-27T10:33:53+01:00Karel KociDoes it make sense to display diagnostic names?Looking in to it.. does it makes sense to display diagnostics names? In most cases I think it is more like internal identifier. I think that rephrasing the description to be more precise for that module and using that instead of just nam...Looking in to it.. does it makes sense to display diagnostics names? In most cases I think it is more like internal identifier. I think that rephrasing the description to be more precise for that module and using that instead of just name might make more sense.
If we need unique identifier for support (to tell them list of diagnostics they need) we might prepend nice name of it in description.https://gitlab.nic.cz/turris/reforis/reforis-diagnostics/-/issues/9Add a warning discouraging users from publicly sharing the diagnostics output2023-01-17T18:10:37+01:00Simon BorekAdd a warning discouraging users from publicly sharing the diagnostics outputAs stated in [our documentation](https://docs.turris.cz/basics/support/): "If you have logs, include them. But be aware that __those might contain sensitive data__."
Warning users directly while generating diagnostics output might be be...As stated in [our documentation](https://docs.turris.cz/basics/support/): "If you have logs, include them. But be aware that __those might contain sensitive data__."
Warning users directly while generating diagnostics output might be beneficial - it would probably lead to a much higher chance of a user being aware of the risks at the time of diagnostics file creation.
Related: https://gitlab.nic.cz/turris/user-docs/-/issues/191