The "Report!" button in the "Report an Incident" form field redirects to a misleading/incomplete message #1706

Open
opened 2012-04-03 17:00:52 +00:00 by zancas · 2 comments

The "report_incident" page that is served as a redirection should say:

"Thank you for your report! It was stored as .flog.bz2 in /logs/incidents. This node has/has not registered with an incident gatherer."
If it has:

"Incident gatherer :"

  • has been contacted
  • has gathered the incident
The "report_incident" page that is served as a redirection should say: "Thank you for your report! It was stored as <incidentid>.flog.bz2 in <HOSTID><BASEDIR>/logs/incidents. This node has/has not registered with an incident gatherer." If it has: "Incident gatherer <incident gatherer name>:" * has been contacted * has gathered the incident
zancas added the
unknown
normal
defect
1.9.1
labels 2012-04-03 17:00:52 +00:00
zancas added this to the undecided milestone 2012-04-03 17:00:52 +00:00
zancas self-assigned this 2012-04-03 17:00:52 +00:00
warner added
code-frontend-web
and removed
unknown
labels 2014-09-11 22:22:06 +00:00

#1974 was mostly a duplicate of this, and was fixed in 30924a506ced5c1f06e034b4f1482217746255ca but I didn't see this ticket until now so I didn't implement the incident gatherer part and I didn't include the filename of the report in the message.

Hopefully an incident report is actually saved to disk even if an incident gatherer is configured? If not, the current message is still incorrect/misleading in the case that an incident gatherer is configured (it says "An incident report has been saved to logs/incidents/ in the node directory").

#1974 was mostly a duplicate of this, and was fixed in 30924a506ced5c1f06e034b4f1482217746255ca but I didn't see this ticket until now so I didn't implement the incident gatherer part and I didn't include the filename of the report in the message. Hopefully an incident report is actually saved to disk even if an incident gatherer is configured? If not, the current message is still incorrect/misleading in the case that an incident gatherer is configured (it says "An incident report has been saved to logs/incidents/ in the node directory").

Incident reports are always written to disk. The gatherer is secondary/supplemental.

We probably don't want to reveal too much about the incident gatherer (like it's IP address), other than it's existence, from the unauthenticated welcome page. Unfortunately I don't think we have a useful "name" for the gatherer anywhere.

Incident reports are always written to disk. The gatherer is secondary/supplemental. We probably don't want to reveal too much about the incident gatherer (like it's IP address), other than it's existence, from the unauthenticated welcome page. Unfortunately I don't think we have a useful "name" for the gatherer anywhere.
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#1706
No description provided.