Graylog Enterprise comes as a set of Graylog server plugins which need to be installed in addition to the Graylog open source setup.
The following list shows the minimum required Graylog versions for the Graylog Enterprise plugins.
|Enterprise Version||Required Graylog Version|
|1.2.0||2.1.0, 2.1.1, 2.1.2|
Since Graylog 2.4 the Graylog Enterprise plugins can be installed the same way Graylog is installed. In most setups this will be done with the package tool provided by the distribution you are using and the online repository.
For previous versions of Graylog Enterprise please contact your Graylog account manager.
Once you installed the Graylog Enterprise plugins you need to obtain a license from the Graylog Enterprise web page.
Should a simple apt-get install graylog-enterprise-plugins or yum install graylog-enterprise-plugins not work for you, the following information might help you.
The Graylog Enterprise plugins need to be installed on all your Graylog nodes!
DEB / RPM Package¶
The default installation should be done with the system package tools. It includes the repository installation that is described in the Operating System Packages installation guides.
When the usage of online repositorys is not possible in your environment, you can download the Graylog Enterprise plugins at https://packages.graylog2.org.
These packages can only be used when you installed Graylog via the Operating System Packages!
The installation on distributions like Debian or Ubuntu can be done with apt-get as installation tool from the previous installed online repository.
$ sudo apt-get install graylog-enterprise-plugins
The installation on distributions like CentOS or RedHat can be done with yum as installation tool from the previous installed online repository.
$ sudo yum install graylog-enterprise-plugins
If you have done a manual installation or want to include only parts of the enterprise plugins you can get the tarball from the download locations listed in the following table.
|Enterprise Version||Download URL|
The tarball includes the enterprise plugin JAR files.
$ tar -tzf graylog-enterprise-plugins-2.5.1.tgz graylog-enterprise-plugins-2.5.1/LICENSE graylog-enterprise-plugins-2.5.1/plugin/graylog-plugin-archive-2.5.1.jar graylog-enterprise-plugins-2.5.1/plugin/graylog-plugin-auditlog-2.5.1.jar graylog-enterprise-plugins-2.5.1/plugin/graylog-plugin-license-2.5.1.jar
Depending on the Graylog setup method you have used, you have to install the plugins into different locations.
|Virtual Machine Appliances||
|Operating System Packages||
Also check the
plugin_dir config option in your Graylog server configuration file. The default might have been changed.
Make sure to install the enterprise plugin JAR files alongside the other Graylog plugins. Your plugin directory should look similar to this after installing the enterprise plugins.
plugin/ ├── graylog-plugin-auditlog-2.5.1.jar ├── graylog-plugin-threatintel-2.5.1.jar ├── graylog-plugin-archive-2.5.1.jar ├── graylog-plugin-beats-2.5.1.jar ├── graylog-plugin-netflow-2.5.1.jar ├── graylog-plugin-aws-2.5.1.jar ├── graylog-plugin-pipeline-processor-2.5.1.jar ├── graylog-plugin-enterprise-integration-2.5.1.jar ├── graylog-plugin-map-widget-2.5.1.jar ├── graylog-plugin-cef-2.5.1.jar ├── graylog-plugin-license-2.5.1.jar └── graylog-plugin-collector-2.5.1.jar
After you installed the Graylog Enterprise plugins you have to restart each of your Graylog servers to load the plugins.
We recommend restarting one server at a time!
You should see something like the following in your Graylog server logs. It indicates that the plugins have been successfully loaded.
2017-12-18T17:39:10.797+01:00 INFO [CmdLineTool] Loaded plugin: AWS plugins 2.5.1 [org.graylog.aws.plugin.AWSPlugin] 2017-12-18T17:39:10.803+01:00 INFO [CmdLineTool] Loaded plugin: Audit Log 2.5.1 [org.graylog.plugins.auditlog.AuditLogPlugin] 2017-12-18T17:39:10.805+01:00 INFO [CmdLineTool] Loaded plugin: Elastic Beats Input 2.5.1 [org.graylog.plugins.beats.BeatsInputPlugin] 2017-12-18T17:39:10.807+01:00 INFO [CmdLineTool] Loaded plugin: CEF Input 2.5.1 [org.graylog.plugins.cef.CEFInputPlugin] 2017-12-18T17:39:10.809+01:00 INFO [CmdLineTool] Loaded plugin: Collector 2.5.1 [org.graylog.plugins.collector.CollectorPlugin] 2017-12-18T17:39:10.811+01:00 INFO [CmdLineTool] Loaded plugin: Enterprise Integration Plugin 2.5.1 [org.graylog.plugins.enterprise_integration.EnterpriseIntegrationPlugin] 2017-12-18T17:39:10.812+01:00 INFO [CmdLineTool] Loaded plugin: License Plugin 2.5.1 [org.graylog.plugins.license.LicensePlugin] 2017-12-18T17:39:10.814+01:00 INFO [CmdLineTool] Loaded plugin: MapWidgetPlugin 2.5.1 [org.graylog.plugins.map.MapWidgetPlugin] 2017-12-18T17:39:10.815+01:00 INFO [CmdLineTool] Loaded plugin: NetFlow Plugin 2.5.1 [org.graylog.plugins.netflow.NetFlowPlugin] 2017-12-18T17:39:10.826+01:00 INFO [CmdLineTool] Loaded plugin: Pipeline Processor Plugin 2.5.1 [org.graylog.plugins.pipelineprocessor.ProcessorPlugin] 2017-12-18T17:39:10.827+01:00 INFO [CmdLineTool] Loaded plugin: Threat Intelligence Plugin 2.5.1 [org.graylog.plugins.threatintel.ThreatIntelPlugin]
If you run a Graylog cluster you need to add the enterprise plugins to every Graylog node. Additionally your load-balancer must route
/api/plugins/org.graylog.plugins.archive/ only to the Graylog master node. Future versions of Graylog will forward these requests automatically to the correct node.
The Graylog Enterprise plugins require a valid license to use the additional features.
Once you have obtained a license you can import it into your Graylog setup by going through the following steps.
- As an admin user, open the System / License page from the menu in the web interface.
- Click the Import new license button in the top right hand corner.
- Copy the license text from the confirmation email and paste it into the text field.
- The license should be valid and a preview of your license details should appear below the text field.
- Click Import to activate the license.
The license automatically applies to all nodes in your cluster without the need to restart your server nodes.
If there are errors, please check that you copied the entire license from the email without line breaks. The same license is also attached as a text file in case it is wrongly formatted in the email.
Some Graylog licenses require to check their validity on a regular basis. This includes the free Graylog Enterprise license with a specific amount of traffic included.
If your network environment requires Graylog to use a proxy server in order to communicate with the external services via HTTPS, you’ll have to configure the proxy server in the Graylog configuration file.
The Graylog web interface shows all details about the license, but if you are still unclear about the requirements, please contact our sales team with your questions.
Details on License Verification¶
Graylog Enterprise periodically sends the following information to ‘api.graylog.com’ via HTTPS on TCP port 443 for each installed license:
- A nonce to avoid modified reports
- The ID of the license
- The ID of the Graylog cluster
- A flag indicating if the license is violated
- A flag indicating if the license has expired
- A flag indicating if Graylog detected that the traffic measuring mechanisms have been modified
- A list of how much traffic was received and written by Graylog in the recent days, in bytes
Details on licensed traffic¶
Graylog has four counters, only the last is counted for the licensed traffic.
the incoming message without any decoding, what is written to the journal before any processing.
the message after the codec of the input has parsed the message (for example syslog parser)
currently, this is stored in memory only and includes the traffic from archive restores.
what is written to Elasticsearch after all processing is done.
Only the Elasticsearch output is measured, all other outgoing traffic does not count. The measurement happens when the message is serialized to elasticsearch. If a message is written to multiple indices the message will count for each index. It does not matter how many copies (replicas) the index has configured as this is done in elasticsearch.
Each of the counters follows these rules:
count the length of the field name.
If the content of the field is a string, the length of the string is counted not the bytes of that string
- for non-string content in the field, the byte length of that content is counted
- byte = 1 byte
- char/short = 2 bytes
- bool/int/floar = 4 bytes
- long/double = 8 bytes
- dates = 8 bytes
all internal fields are not countent (those meta information that are created by Graylog)