Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • rdsys rdsys
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 43
    • Issues 43
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • rdsysrdsys
  • Issues
  • #13
Closed
Open
Created Oct 16, 2020 by Philipp Winter@phwReporter

Monitor rdsys using monit

Let's create monitoring targets for rdsys once it's deployed. Here's what's worth monitoring:

  1. Rdsys's distributors, e.g. HTTPS and Salmon. Each of these distributors is a separate process and can die independently.
  2. Rdsys's backend. Its registration API is open to the public and would be a great monitoring target.
Edited Jan 12, 2021 by Philipp Winter
Assignee
Assign to
Time tracking