====== Collectors ======

===== Purpose =====

  A collector is a remote service that acts as a proxy between the Redpeaks Cockpit and SAP systems.
  It provides the means to control the monitoring configuration of remote SAP systems and to collect monitoring data.
  By using multiple collectors, you can centrally monitor several isolated environments.
  Simply assign groups of systems to a collector to start controlling remote target SAP systems.

===== Configuration =====

  * Collectors will be automatically displayed in the collectors table as soon as the connection is configured and established with the remote collector service.

{{:products:cockpit:1.0:userguide:settings:collector_page_main.png?900|}}

^ Menu ^ Description ^
| [[.:agents:registered_collectors|Registered collectors]] | Lists collectors currently and previously discovered |
| [[.:agents:collector_associations|Collector associations]] | Associate a collector with one or several system groups |
| [[.:agents:group_associations|Group associations]] | Associate a group with one or several collectors |
| [[.:agents:collector_profiles|Collector profiles]] | Define reusable configuration templates to apply across multiple collectors |
| [[.:agents:api_keys|API Keys]] | List and manage the API keys used by collectors to authenticate |
| [[.:agents:drivers|Drivers]] | Centrally manage and distribute drivers to collectors |
| [[.:agents:statistics|Statistics]] | Display real-time performance statistics for each collector |
| [[.:agents:monitoring|Monitoring]] | Define collector health monitoring settings |

===== Notes =====

  * Any change in the monitoring configuration will be automatically detected and transferred to the relevant collector within the next 30 seconds.
  * Monitoring settings (Monitoring tab) are also propagated to collectors within 30 seconds of modification.
  * Collector memory and thread settings should only be changed when a collector is configured to monitor more than 100 systems.