Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 917
    • Issues 917
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 17
    • Merge requests 17
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #12262
Closed
Open
Created Feb 25, 2017 by anonym@anonymMaintainer

Make WhisperBack logs available to developers to query

Originally created by @anonym on #12262 (Redmine)

I’m finding more and more uses for greping our WhisperBack logs to collect aggregated statistics about our users, mostly related to hardware support, what Tails features are used, and frequency about certain non-fatal errors. The problem is that I don’t have it myself, and instead have to ask sajolida or someone from frontdesk to do the query for me.

As a Tails developer I’d find it useful to be able to do such queries myself. At first I thought an encrypted Git repo would be perfect, but then I realized that retaining this sensitive user-submitted data forever is irresponsible. I’m not even sure we have a data retention policy (?). Any way, I’d be happy with data from the past two years.

Regarding implementation, it’d be cool if the tails-bugs@ Schleuder could archive all user emails somewhere (and we’d seed it with old email from frontdesk’s inboxes) available to rsync with + a cron job that removes too old emails to enforce the data retention policy. Or something equivalent.

Note: intrigeri suggested to “subscribe to [the tails-bugs] list, filter email to a folder + auto-mark as read, and you’ll have that for the future?”. I guess I’ll do (+ ask for a dump of tails-bugs@ from frontdesk) that if this ticket is rejected, but I’d find a solution that has the data retention angle incorporated better, and that can be reused by other developers. So, yeah, I’ll do that if we reject this idea, but I don’t think it’s a good solution.

Related issues

  • Related to #9960 (closed)
  • Related to #9803 (closed)
Edited May 15, 2020 by anonym
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking