Some Basic Questions

I am looking for a monitor tool for my Drupal instances that covers the following:
- Is a website accessible, if not, alarm me
- Website/Server data like PHP, OS version etc.
- Drupal data such as whether certain modules are activated or not
- Maintenance stuff

DRD is a dashboard tool which is Drupal specific and it collects Drupal specific data from remote Drupal sites to display them altogether in one place. That includes all of the information that you can find on the status report of each individual Drupal site, it also contains the list and versions of enabled modules.

To monitor the responses to http requests, DRD is not the right tool. Uptime monitoring has totally different paradigms and is in no way Drupal specific, so I recommend using tools like Update Monitor or Uptime Kuma, etc.

According to the statistics on Drupal.org, why do so many more people have DRD Agend installed (3'245 sites) instead of Drupal Remote Dashboard (129 sites)? Is it because people are using DRD Agend to send Drupal specific data to other monitoring systems?

Each Drupal agency requires one (1) instance of DRD to monitor and number of remote Drupal sites, each of which has to have the DRD agent installed. With the numbers above it looks like 129 agencies are using DRD and they monitor 25 remote site in average. More likely, that most of them monitor only a handful of sites, and other may monitor hundreds of them.

How much does DRD cooperate with this module: https://www.drupal.org/project/automatic_updates → ? So can you do updates automatically with DRD or should that be done separately with the other module?

There is no connection between the 2 (yet). DRD is around for 15 years already. Automatic Updates is only about to get ready.

What are the biggest advantages of the module that are unique?

You get a single place where you can go to get all the important Drupal sites that you're responsible for. This, combined with the fact that you own your data and don't have to give any third party access to your servers, is the biggest advantage to us, why we've built it in the first place.

What are the biggest disadvantages of the module? Perhaps dependencies and performance?

Nothing comes to mind.

@jurgenhaas Thank you very much for answering all the questions. You have helped me a lot and the answers are conclusive :)
Perhaps the one or other question & answer can still be included in the documentation, if it isn't already and I just haven't seen it.
Thanks again

Thanks for your feedback.

Perhaps the one or other question & answer can still be included in the documentation, if it isn't already, and I just haven't seen it.

It's all about limited resources. But the good thing is, documentation is also open for collaboration. Let's hope someone is willing to add this there.

Automatically closed - issue fixed for 2 weeks with no activity.