Status Dashboard module: Why and how does it differ from DRD?

Looks like one big difference between these two is that DRD Dashboard pulls from client agent sites (see https://www.drupal.org/docs/contributed-modules/drupal-remote-dashboard/... → ) whereas Status Dashboard clients push up to Dashboard. I think security and network configuration complexity might be a differentiating consideration for some users who implement one of these modules: How many individual client firewalls may need to be adjusted?

One major difference between the two Drupal Site Status Dashboard modules is complexity and capability: DRD seems to be able to do a whole lot, while Status Dashboard looks focused on basics like "installed modules, available updates, core version." DRD is also potentially quite complex and was, honestly, a bit of a walk of faith to set up, whereas Status Dashboard was so so so simple out of the box.

I don't think Status Dashboard provides remote watchdog/dblog but DRD does. Also, DRD provides literally the `/admin/reports/status` page of info like php, mysql, and core versions, warnings, errors, and module-specific warnings, but Status Dashboard does not appear to.

Hello, @texas-bronius!
Looks like you've answered your own question) Indeed, Status Dashboard modules much simpler than DRD both in implementation and setup, that's because of main purpose of Status Dashboard module - just monitor updates across supported websites.
Before developing this module, an attempt was done to set up desired update notification system using DRD, but it appeared to be a huge overhead for such simple task.
I don't see any need to update summary of Status Dashboard modules according to that issue, so closing this as "works as designed"