microsoft-sentinel-log-analytics-logstash-output-plugin 2.4.0-java → 2.5.0-java

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 52fc2d58edeab5e2a9d529828781d2f958a33c145c46ef05587a65407ea2e551
-  data.tar.gz: 781cf13f7ac5e4964cd3d628c8261b01034d31d0b8d03100d410f99690788a6d
+  metadata.gz: b9de662d1b2a1b355e807bc3eb0ffb51dcf40e62b4e0f2a1c0b36477624a8b73
+  data.tar.gz: 3be11c0d54fc160d88ebecf8d9bf0821faf286dbc82af1934149698515699204
 SHA512:
-  metadata.gz: 63dba7974498e08c48d04c410c2cafb3f6e37c7e2b7e52a9a43fe88c581a4eb686324e69fcb84cad5e79c4533f85165edd4d142823bc35acd9e76b2ec1d08e56
-  data.tar.gz: 27288003dce4595b3c81a22a7685d1684d74a91b153dcf46814ef7204a6a94fcc2edc54f9248bd50a96b6434a15416628b8f1590ea30357857605c02b69ec7b1
+  metadata.gz: 2a206bc526a9068cfb35872399769e5da7dcd022b151f1459fec2c87db4704c986bfb168be497bf108fe085b296f0df2d44c1fc40fab03b7c7bc8cf075170ab1
+  data.tar.gz: c70d3cdf492dff244f511c35b720f96b6b7a1d0ac9c4e3b9bf9356b4c08314961a55fb3a08a4f3ab744f8a50e1d2d403660b0e9817d808788409ed59dfdd3f7f

data/CHANGELOG.md

@@ -1,3 +1,8 @@
+## 2.5.0
+- Added optional per-plugin proxy configuration for authentication and ingestion traffic using `proxy`, `proxy_aad`, and `proxy_endpoint`.
+- Updated Netty handler, HTTP, HTTP/2, and DNS components to 4.1.136.Final.
+- Updated Jackson Databind and Jackson Core to 2.18.8.
+
 ## 2.4.0
 - Worker threads now run as bounded, executor-scheduled passes: recoverable exceptions are logged and the worker resumes on the next cycle; fatal JVM errors are logged and re-thrown.
 - Fixed graceful shutdown so in-flight batches are drained (batchers, then unifiers, then senders) before workers stop, bounded by `max_graceful_shutdown_time_seconds`.
@@ -35,4 +40,7 @@
 
 ## 2.0.0
 - Refactored the plugin from Ruby to Java.
-- Added ManagedIdentity authentication.
+- Added ManagedIdentity authentication.
+
+## 1.x.x (Ruby - deprecated)
+The 1.x.x releases are the deprecated Ruby version of this plugin. For the 1.x.x changelog and documentation, see [microsoft-sentinel-log-analytics-logstash-output-plugin](../microsoft-sentinel-log-analytics-logstash-output-plugin/CHANGELOG.md).

data/README.md

@@ -3,8 +3,8 @@
 Microsoft Sentinel provides a new output plugin for Logstash. Use this output plugin to send any log via Logstash to the Microsoft Sentinel/Log Analytics workspace. This is done with the Log Analytics DCR-based API.
 You may send logs to custom or standard tables.  
 
-Plugin version: v2.3.3  
-Released on: 2026-07-02  
+Plugin version: v2.5.0  
+Released on: 2026-08-04  
 
 This plugin is currently in development and is free to use. We request and appreciate feedback from users.  
 
@@ -19,7 +19,7 @@ This plugin is currently in development and is free to use. We request and appre
 
 Microsoft Sentinel provides Logstash output plugin to Log analytics workspace using DCR based logs API.  
 
-The plugin is published on [RubyGems](https://rubygems.org/gems/microsoft-sentinel-log-analytics-logstash-output-plugin/versions/2.2.2-java). To install to an existing logstash installation, run `logstash-plugin install microsoft-sentinel-log-analytics-logstash-output-plugin`.  
+The plugin is published on [RubyGems](https://rubygems.org/gems/microsoft-sentinel-log-analytics-logstash-output-plugin/versions/2.5.0-java). To install to an existing logstash installation, run `logstash-plugin install microsoft-sentinel-log-analytics-logstash-output-plugin`.  
 
 If you do not have a direct internet connection, you can install the plugin to another logstash installation, and then export and import a plugin bundle to the offline host. For more information, see [Logstash Offline Plugin Management instruction](<https://www.elastic.co/guide/en/logstash/current/offline-plugins.html>).  
 
@@ -55,7 +55,7 @@ Note: make sure that the path exists before creating the sample file.
 ### Configurations:
 The following parameters are optional and should be used to create a sample file.  
 - **create_sample_file** - Boolean, False by default. When enabled, up to 10 events will be written to a sample json file.  
-- **sample_file_path** - Number, Empty by default. Required when create_sample_file is enabled. Should include a valid path in which to place the sample file generated.  
+- **sample_file_path** - String, Empty by default. Required when create_sample_file is enabled. Should include a valid path in which to place the sample file generated.  
 
 ### Complete example
 1. set the pipeline.conf with the following configuration:  
@@ -210,6 +210,9 @@ A complete `logstash.conf` using client secret auth with a Beats input:
 | Key | Default | Description |  
 |---|---|---|  
 | `azure_cloud` | `AzurePublicCloud` | Azure cloud environment |  
+| `proxy` | *(none)* | Optional. Base HTTP proxy URL applied to all plugin traffic. Format: `[http://][user:password@]host:port`. When unset, no proxy is used and behavior is unchanged |  
+| `proxy_aad` | *(value of `proxy`)* | Optional. HTTP proxy URL used only for Microsoft Entra ID (AAD) authentication/token traffic. Falls back to `proxy` when unset |  
+| `proxy_endpoint` | *(value of `proxy`)* | Optional. HTTP proxy URL used only for traffic to the Data Collection Endpoint. Falls back to `proxy` when unset |  
 | `keys_to_keep` | *(all)* | Array of field names to send (subset filtering) |  
 | `max_retries_num` | `3` | Max retry attempts for failed sends |  
 | `initial_wait_time_seconds` | `1` | Initial backoff between retries |  
@@ -227,6 +230,30 @@ A complete `logstash.conf` using client secret auth with a Beats input:
 | `unifier_workers_count` | *(auto)* | Number of unifier threads |  
 | `id` | `None` | A custom identification tag to be added to sent-batches logs |  
 
+### Proxy configuration
+
+The proxy settings are **optional** and scoped to this plugin only. If you do not set any of them, the plugin behaves exactly as before and sends traffic directly (no proxy). This is useful when a single Logstash instance has multiple outputs and only the Microsoft Sentinel output needs to traverse a corporate proxy.
+
+- `proxy` — base proxy applied to both authentication and ingestion traffic.
+- `proxy_aad` — overrides the proxy used for Microsoft Entra ID (AAD) token requests; falls back to `proxy`.
+- `proxy_endpoint` — overrides the proxy used for Data Collection Endpoint traffic; falls back to `proxy`.
+
+Proxy URLs use the format `[http://][user:password@]host:port`. The scheme is optional and defaults to `http`; both host and port are required. Example:
+
+    output {
+      microsoft-sentinel-log-analytics-logstash-output-plugin {
+        data_collection_endpoint => "https://my-dce.eastus2-1.ingest.monitor.azure.com"
+        dcr_id                   => "dcr-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
+        stream_name              => "Custom-MyTableRawData_CL"
+        client_id                => "<your-app-client-id>"
+        client_secret            => "<your-app-client-secret>"
+        tenant_id                => "<your-azure-tenant-id>"
+        proxy                    => "http://proxyhost:8080"
+      }
+    }
+
+Security note: if your proxy requires credentials, store them in the Logstash KeyStore rather than placing them in plaintext in the configuration file.
+
 ## Known issues
  
 When using Logstash installed on a Docker image of Lite Ubuntu, the following warning may appear:  

data/VERSION

@@ -1 +1 @@
-2.4.0
+2.5.0

data/lib/microsoft-sentinel-log-analytics-logstash-output-plugin_jars.rb

@@ -2,4 +2,4 @@
 # encoding: utf-8
 
 require 'jar_dependencies'
-require_jar('org.logstashplugins', 'microsoft-sentinel-log-analytics-logstash-output-plugin', '2.4.0')
+require_jar('org.logstashplugins', 'microsoft-sentinel-log-analytics-logstash-output-plugin', '2.5.0')

data/logstash-output-microsoft-sentinel-log-analytics-logstash-output-plugin.gemspec

@@ -1,7 +1,7 @@
 # AUTOGENERATED BY THE GRADLE SCRIPT. EDITS WILL BE OVERWRITTEN.
 Gem::Specification.new do |s|
   s.name            = 'microsoft-sentinel-log-analytics-logstash-output-plugin'
-  s.version         = '2.4.0'
+  s.version         = '2.5.0'
   s.licenses        = ['Apache-2.0']
   s.summary         = 'Microsoft Sentinel Log Analytics output plugin'
   s.description     = 'Microsoft Sentinel provides a new output plugin for Logstash. Use this output plugin to send any log via Logstash to the Microsoft Sentinel/Log Analytics workspace. This is done with the Log Analytics DCR-based API.'

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: microsoft-sentinel-log-analytics-logstash-output-plugin
 version: !ruby/object:Gem::Version
-  version: 2.4.0
+  version: 2.5.0
 platform: java
 authors:
 - Microsoft
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-07-10 00:00:00.000000000 Z
+date: 2026-08-04 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   requirement: !ruby/object:Gem::Requirement
@@ -75,7 +75,7 @@ files:
 - lib/logstash_registry.rb
 - lib/microsoft-sentinel-log-analytics-logstash-output-plugin_jars.rb
 - logstash-output-microsoft-sentinel-log-analytics-logstash-output-plugin.gemspec
-- vendor/jar-dependencies/org/logstashplugins/microsoft-sentinel-log-analytics-logstash-output-plugin/2.4.0/microsoft-sentinel-log-analytics-logstash-output-plugin-2.4.0.jar
+- vendor/jar-dependencies/org/logstashplugins/microsoft-sentinel-log-analytics-logstash-output-plugin/2.5.0/microsoft-sentinel-log-analytics-logstash-output-plugin-2.5.0.jar
 homepage:
 licenses:
 - Apache-2.0