When the collector tries to register with Sumo it first sends the request to the US1 deployment. When you start up an Installed Collector for the first time it registers with Sumo and creates any Sources that you have defined in a UTF-8 encoded JSON source configuration file. This section is an overview of how Installed Collectors and their Sources operate. Installed Collectors and Sources in action Note that if you provide the Sources configuration in a JSON file, you can no longer manage the Sources through the Sumo web app or the Collector Management API. For more information, see Use JSON to Configure For source-specific instructions, see the topics below Sources for Installed Collectors.Īlternatively, you can define Sources for an Installed Collector in a UTF-8 encoded JSON file, in which case you must provide the file when starting the Collector for the first time. You can create Sources using the Sumo web app at any time after Collector installation. You can optionally configure a denylist of files to exclude from collection. When you configure Sources that read from log files, you specify a path expression that defines what files to scan. The more Sources you set up, the easier it is to isolate one of the Sources in a search since each Source can be identified by its metadata. For example, you might set up three Local File Sources to collect router activity logs from three locations, and another Local File Source to collect logs from a web application.Įach Source is tagged with its own metadata, as described in Metadata Naming Conventions. A Source should be configured to collect similar data types. You can set up as many as 1,000 Sources on a given Collector. For more information, see Collector API Methods and Examples. You can update the configuration of an Installed Collector using the Collector Management API. ![]() For more information, see user.properties parameters.Ī few Installed Collector behaviors, such as caching, are configured in the collector.properties file in the Collector’s config directory. The binary package can also be used on MacOS.įor details on Collector installation, see Install a Collector on Linux, Install a Collector on MacOS, and Install a Collector on Windows.Īfter a Collector is up and running, you can change some Installed Collector configuration settings by editing user.properties and restarting the collector. You supply configuration settings in a user.properties file that you create. the installer writes these settings to user.properties in the collector’s /config directory. You supply configuration settings on the command line, or using a varfile. The installer writes these settings to user.properties in the collector’s /config directory. UI installers. You provide configuration settings during the installation dialog.Sumo provides multiple methods for installing a Collector: Collector installation and configuration Installing and configuring Collectors and Sources. This section is an overview of the multiple methods Sumo provides for Generally, as the number of Sources increases, the number of threads also increases. The Collector will use three threads per available CPU by default, you can increase the max threads if needed.ġ,000 events per second with 1 KB message size: Number of Local File Sourcesĥ,000 events per second with 1 KB message size: Number of Local File Sourcesġ0,000 events per second with 1 KB message size: Number of Local File SourcesĪbout Collector and Source installation and configuration The columns are the Average CPU and Average Message Size. Whereas, 1 KB of logs can be ingested at 500 logs per second ( 500 KB/sec).Įvents Per Second (EPS) achieved by message size and CPU usage: Size of messages Īn Installed Collector performs better when collecting larger sized log messages. For example, at 5% CPU usage 10 KB of logs can be ingested at 100 logs per second ( 1,000 KB/sec). The following data was generated from a Collector on an Amazon EC2 m4.large instance type with 2 virtual CPUs and 8 GiB of memory. Use the following observations to guide you when designing your deployment. The Collector can try to keep CPU usage at a targeted percentage when using Local and Remote File Sources.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |