search

netdata / netdata

Architected for speed. Automated for easy. Monitoring and troubleshooting, transformed!
https://www.netdata.cloud
GNU General Public License v3.0
72.27k stars 5.95k forks source link

Docs: Group collectors by type #8069

Closed joelhans closed 4 years ago

joelhans commented 4 years ago

During the work involved in #7878 / #7996, we decided that grouping collectors by type, rather than their plugin/orchestrator, was too much of a task for the current sprint. So, this issue will serve as the place where we can discuss how to organize collectors by type and manage the work of editing collectors/COLLECTORS.md into a list that's organized by type.

@ilyam8 can comment below about his specific concerns with the grouping by type that currently exists on the main README, the homepage, and in docs/Add-more-charts-to-netdata.md. Generally speaking, some of the types were not accurate, and there were instances of certain collectors being associated with the wrong type.

TODOs:

ilyam8 commented 4 years ago

Initial break down of external modules by monitoring area. It is far from good/complete, should be adjusted.

We need to add internal collectors and build a good and not complex structure.

Top levels should be something like:

Any help appreciated.

cc @joelhans @manos-saratsis

Feel free to change the lists below.

btw duplicates are ok, they are py/go modules (same name).

Application metrics

Databases and key-value stores

Search engines

Web servers, caching proxy servers, and load balancers

HTTP/TCP endpoint availability

Virtualization and containers

Storage systems

Messaging systems

Email servers

DNS servers

DHCP

Virtual private networks (VPN)

AAA servers

Application performance monitoring (APM)

Kubernetes control plane

Distributed computing

Log analysis applications

Time servers

Digital certificates

Media streaming servers

Provisioning systems

Telephony servers

Game servers

System monitoring applications

Social sharing servers

System security

Advertisement and tracker blocker applications

APIs

Windows machines

Remote device and sensor metrics

joelhans commented 4 years ago

@ilyam8 I edited your list with a few changes:

I don't have any immediate objections to how you've organized the types, but I also don't know nearly as much about this as you do. It looks fine to me.

I'm struggling to think about how we add all the things our internal plugins monitor without this list being ridiculously large. proc.plugin alone monitors like 20 different things.

ilyam8 commented 4 years ago

add all the things our internal plugins monitor without this list being ridiculously large

Yes, i think about it too. If the goal is to have a long list to provide wow effect we need to put all of them.

There is datadog integrations page:

https://docs.datadoghq.com/integrations/

It is a flat "list", all system metrics (most of our internal plugins collect system metrics) are under system intergration, it is just a one item.

joelhans commented 4 years ago

Working on this list of system metrics...

System metrics

System resources

Memory

Disks

Filesystems

Networking

Processes

System hardware and sensors

System users

stale[bot] commented 4 years ago

This issue has been inactive for 30 days. It will be closed in one week, unless it is updated.

joelhans commented 4 years ago

Just realized that we fixed this a while back with #9513. Closing.