Merge pull request #72 from netscaler/nsoe-1.9.001

Releasing NSOE v1.9.001

Author: subashd

docs/deploy-coe-with-Kafka.md

@@ -315,6 +315,10 @@ The following example shows the YAML file with the data format configured as JSO
                     "SLA": "none",
                     "MONGO": "none"
                 }
+                "TimeSeries": {
+                    "EVENTS": "yes",
+                    "AUDITLOGS": "yes"
+                }
               }
           }
         }

docs/field-descriptions.md

@@ -77,16 +77,20 @@ This topic contains descriptions of the `lstreamd_default.conf` file parameters.
 
 -  `EVENTS`:
 
-    Citrix ADC Observability Exporter allows exporting time series ( events, and audit logs) to Splunk.
+    Citrix ADC Observability Exporter allows exporting time series (events, and audit logs) to Splunk and Kafka.
     Set this field to `yes` to allow exporting events.
     The default value is `no`.
 
 -  `AUDITLOGS`:
 
-    You can export audit logs to Splunk.
+    You can export audit logs to Splunk and Kafka.
     Set this field to `yes` to allow exporting audit logs.
     The default value is `no`.
 
+-  `ConnectionPoolSize`:
+
+    Alters the size of connection pools for Splunk.`ConnectionPoolSize` and `MaxConnections` can be used to control the rate at which data is exported (to the endpoint).
+
 -  `ElkMaxSendBuffersPerSec`:
 
     The maximum rate at which the data is exported to ElasticSearch.
@@ -174,7 +178,7 @@ Following are the guidelines while configuring the  `lstreamd_default.conf` file
 
     Prometheus is always `ON` and metrics can be exported to it in parallel to transactions, audit logs, and events.
 
--  Currently, you can only export time series like audit logs and events to Splunk, but in parallel to transactions and metrics.
+-  Currently, you can only export time series like audit logs and events to Splunk and Kafka, but in parallel to transactions and metrics.
 
 -  You must not configure multiple endpoints of the same type in the `lstreamd_default.conf` file for one Citrix ADC Observability Exporter. For example, it is not possible to configure two Splunk instances, or two Kafka instances, or two ElasticSearch instances, or one Splunk and one ElasticSearch, and so on.
     For Zipkin, although you can configure it in parallel to Splunk and ElasticSearch, you may not configure multiple instances of Zipkin. For example, it is not possible to have two Zipkin instances in parallel.

docs/index.md

@@ -44,9 +44,9 @@ You can view the traces using the Zipkin user interface. However, you can also e
 
 When Elasticsearch is specified as the transaction endpoint, Citrix ADC Observability Exporter converts the data to JSON format. On the Elasticsearch server, Citrix ADC Observability Exporter creates Elasticsearch indexes for each ADC on an hourly basis. These indexes are based on data, hour, UUID of the ADC, and the type of HTTP data (http_event or http_error). Then, Citrix ADC Observability Exporter uploads the data in JSON format under Elastic search indexes for each ADC. All regular transactions are placed into the http_event index and any anomalies are placed into the http_error index.  
 
-### Citrix ADC Observability Exporter with Kafka as the transaction endpoint
+### Citrix ADC Observability Exporter with Kafka as the endpoint
 
-When Kafka is specified as the transaction endpoint, Citrix ADC Observability Exporter converts the transaction data to [Avro](http://avro.apache.org/docs/current/Avro) format and streams them to Kafka.
+NetScaler Observability Exporter exports transactions to Kafka as [Avro](http://avro.apache.org/docs/current/Avro) or JSON. Auditlogs and events are exported as JSON.
 
 ### Citrix ADC Observability Exporter with Prometheus as the endpoint for time series data