Sha256: 86e8292baf1b1fcfa7f7383972d93915e43c876eaaee6f131b9a73aa5288a144
Contents?: true
Size: 1.45 KB
Versions: 5
Compression:
Stored size: 1.45 KB
Contents
# Changelog # 2.0.3 - Make JSON mapping optional # 2.0.2 - Bugfix for the scenario where the plugin uses managed identity. Instead of providing the managed identity name as empty in the config, it can completely be skipped # 2.0.0 - Use (5.0.2) version of the java sdk, and retrieve it from maven with bundler. Supports logstash 8.6 versions and up - Upgrade to latest Java SDK fixes [CVE](https://github.com/advisories/GHSA-599f-7c49-w659) and addresses Issue#48 # 1.0.5 - Use (3.1.3) version of the java sdk, and retrieve it from maven with bundler. - Added support for `proxy_host` `proxy_port` `proxy_protocol` to support proxying ingestion to Kusto # 1.0.0 - Use stable (2.1.2) version of the java sdk, and retrieve it from maven with bundler. - Renamed `mapping` to `json_mapping` in order to clarify usage. `mapping` still remains as a deprecated parameter. ## 0.4.0 - set 'client name for tracing' to identify usage of this plugin on Kusto logs ## 0.3.0 - move to version 1.0.0-BETA-04 of azure-kusto-java sdk - better support multiple kusto outputs running in parallel ## 0.2.0 - move to version 1.0.0-BETA-01 of azure-kusto-java sdk ## 0.1.7 - fixed app_key (password) bug, include 0.1.7 of the kusto-java-sdk to allow working through a proxy ## 0.1.6 - plugin published to the public. supports ingestion json events into a specific table-database (without dynamic routing currently) ## 0.1.0 - Plugin created with the logstash plugin generator
Version data entries
5 entries across 5 versions & 1 rubygems