Azure Firewall logs

Azure firewall logs integration


Version	1.9.1 (View all)
Compatible Kibana version(s)	8.12.0 or higher
Supported Serverless project types What's this?	Security Observability
Subscription level What's this?	Basic

Azure Firewall Logs are records of events such as network and application rules that occur within your Azure Firewalls. They provide visibility and can be used to troubleshoot issues related to access, conectivity or performance.

Supported log categories:

Log Category	Description
AzureFirewallApplicationRule	These logs capture information about the traffic that is allowed or denied by application rules configured in Azure Firewall.
AzureFirewallNetworkRule	These logs capture information about the traffic that is allowed or denied by network rules configured in Azure Firewall.
AzureFirewallDnsProxy	These logs capture information about DNS requests and responses that are processed by Azure Firewall's DNS proxy.

Requirements and setup

Refer to the Azure Logs page for more information about setting up and using this integration.

Settings

eventhub : string An Event Hub is a fully managed, real-time data ingestion service. Elastic recommends using only letters, numbers, and the hyphen (-) character for Event Hub names to maximize compatibility. You can use existing Event Hubs having underscores (_) in the Event Hub name; in this case, the integration will replace underscores with hyphens (-) when it uses the Event Hub name to create dependent Azure resources behind the scenes (e.g., the storage account container to store Event Hub consumer offsets). Elastic also recommends using a separate event hub for each log type as the field mappings of each log type differ. Default value insights-operational-logs.

consumer_group : string The publish/subscribe mechanism of Event Hubs is enabled through consumer groups. A consumer group is a view (state, position, or offset) of an entire event hub. Consumer groups enable multiple consuming applications to each have a separate view of the event stream, and to read the stream independently at their own pace and with their own offsets. Default value: $Default

connection_string : string The connection string is required to communicate with Event Hubs, see steps here.

A Blob Storage account is required in order to store/retrieve/update the offset or state of the eventhub messages. This means that after stopping the Azure logs package it can start back up at the spot that it stopped processing messages.

storage_account : string The name of the storage account where the state/offsets will be stored and updated.

storage_account_key : string The storage account key, this key will be used to authorize access to data in your storage account.

storage_account_container : string The storage account container where the integration stores the checkpoint data for the consumer group. It is an advanced option to use with extreme care. You MUST use a dedicated storage account container for each Azure log type (activity, sign-in, audit logs, and others). DO NOT REUSE the same container name for more than one Azure log type. See Container Names for details on naming rules from Microsoft. The integration generates a default container name if not specified.

resource_manager_endpoint : string Optional, by default we are using the azure public environment, to override, users can provide a specific resource manager endpoint in order to use a different azure environment.

Resource manager endpoints:

# Azure ChinaCloud
https://management.chinacloudapi.cn/

# Azure GermanCloud
https://management.microsoftazure.de/

# Azure PublicCloud 
https://management.azure.com/

# Azure USGovernmentCloud
https://management.usgovcloudapi.net/

Logs

firewall_logs

The firewall_logs data stream of the Azure Logs package will collect any firewall log events that have been streamed through an Azure event hub.

An example event for firewall looks as following:

{
    "@timestamp": "2022-06-08T16:54:58.849Z",
    "azure": {
        "firewall": {
            "action": "Deny",
            "category": "AzureFirewallNetworkRule",
            "icmp": {
                "request": {
                    "code": "8"
                }
            },
            "operation_name": "AzureFirewallNetworkRuleLog"
        },
        "resource": {
            "group": "TEST-FW-RG",
            "id": "/SUBSCRIPTIONS/23103928-B2CF-472A-8CDB-0146E2849129/RESOURCEGROUPS/TEST-FW-RG/PROVIDERS/MICROSOFT.NETWORK/AZUREFIREWALLS/TEST-FW01",
            "name": "TEST-FW01",
            "provider": "MICROSOFT.NETWORK/AZUREFIREWALLS"
        },
        "subscription_id": "23103928-B2CF-472A-8CDB-0146E2849129"
    },
    "cloud": {
        "account": {
            "id": "23103928-B2CF-472A-8CDB-0146E2849129"
        },
        "provider": "azure"
    },
    "destination": {
        "address": "89.160.20.156",
        "as": {
            "number": 29518,
            "organization": {
                "name": "Bredband2 AB"
            }
        },
        "geo": {
            "city_name": "Linköping",
            "continent_name": "Europe",
            "country_iso_code": "SE",
            "country_name": "Sweden",
            "location": {
                "lat": 58.4167,
                "lon": 15.6167
            },
            "region_iso_code": "SE-E",
            "region_name": "Östergötland County"
        },
        "ip": "89.160.20.156"
    },
    "ecs": {
        "version": "8.3.0"
    },
    "event": {
        "category": [
            "network"
        ],
        "kind": "event",
        "original": "{\"category\":\"AzureFirewallNetworkRule\",\"operationName\":\"AzureFirewallNetworkRuleLog\",\"properties\":{\"msg\":\"ICMP Type=8 request from 192.168.0.2 to 89.160.20.156. Action: Deny. \"},\"resourceId\":\"/SUBSCRIPTIONS/23103928-B2CF-472A-8CDB-0146E2849129/RESOURCEGROUPS/TEST-FW-RG/PROVIDERS/MICROSOFT.NETWORK/AZUREFIREWALLS/TEST-FW01\",\"time\":\"2022-06-08T16:54:58.8492560Z\"}",
        "type": [
            "connection",
            "denied"
        ]
    },
    "network": {
        "transport": "icmp"
    },
    "observer": {
        "name": "TEST-FW01",
        "product": "Network Firewall",
        "type": "firewall",
        "vendor": "Azure"
    },
    "related": {
        "ip": [
            "192.168.0.2",
            "89.160.20.156"
        ]
    },
    "source": {
        "address": "192.168.0.2",
        "ip": "192.168.0.2"
    },
    "tags": [
        "preserve_original_event"
    ]
}

Exported fields

Field	Description	Type
@timestamp	Event timestamp.	date
azure.correlation_id	Correlation ID	keyword
azure.firewall.action	Firewall action taken	keyword
azure.firewall.category	Category	keyword
azure.firewall.dnssec_bool_flag	True if DNS request is using DNSSEC	boolean
azure.firewall.dnssec_buffer_size	Size of the DNSSEC buffer	long
azure.firewall.duration	Duration of the firewall request	keyword
azure.firewall.event_original_uid	UID assigned to the logged event	keyword
azure.firewall.icmp.request.code	ICMP request code	keyword
azure.firewall.identity_name	identity name	keyword
azure.firewall.operation_name	Operation name	keyword
azure.firewall.policy	Name of firewall policy containing the matched rule	keyword
azure.firewall.rule_collection_group	Name of rule collection group containing the matched rule - name: icmp	keyword
azure.resource.authorization_rule	Authorization rule	keyword
azure.resource.group	Resource group	keyword
azure.resource.id	Resource ID	keyword
azure.resource.name	Name	keyword
azure.resource.namespace	Resource type/namespace	keyword
azure.resource.provider	Resource type/namespace	keyword
azure.subscription_id	Azure subscription ID	keyword
azure.tenant_id	tenant ID	keyword
cloud.account.id	The cloud account or organization id used to identify different entities in a multi-tenant environment. Examples: AWS account id, Google Cloud ORG Id, or other unique identifier.	keyword
cloud.provider	Name of the cloud provider. Example values are aws, azure, gcp, or digitalocean.	keyword
data_stream.dataset	Data stream dataset.	constant_keyword
data_stream.namespace	Data stream namespace.	constant_keyword
data_stream.type	Data stream type.	constant_keyword
destination.address	Some event destination addresses are defined ambiguously. The event will sometimes list an IP, a domain or a unix socket. You should always store the raw address in the `.address` field. Then it should be duplicated to `.ip` or `.domain`, depending on which one it is.	keyword
destination.as.number	Unique number allocated to the autonomous system. The autonomous system number (ASN) uniquely identifies each network on the Internet.	long
destination.as.organization.name	Organization name.	keyword
destination.as.organization.name.text	Multi-field of `destination.as.organization.name`.	match_only_text
destination.bytes	Bytes sent from the destination to the source.	long
destination.domain	The domain name of the destination system. This value may be a host name, a fully qualified domain name, or another host naming format. The value may derive from the original event or be added from enrichment.	keyword
destination.geo.city_name	City name.	keyword
destination.geo.continent_name	Name of the continent.	keyword
destination.geo.country_iso_code	Country ISO code.	keyword
destination.geo.country_name	Country name.	keyword
destination.geo.location	Longitude and latitude.	geo_point
destination.geo.name	User-defined description of a location, at the level of granularity they care about. Could be the name of their data centers, the floor number, if this describes a local physical entity, city names. Not typically used in automated geolocation.	keyword
destination.geo.region_iso_code	Region ISO code.	keyword
destination.geo.region_name	Region name.	keyword
destination.ip	IP address of the destination (IPv4 or IPv6).	ip
destination.nat.ip	Translated ip of destination based NAT sessions (e.g. internet to private DMZ) Typically used with load balancers, firewalls, or routers.	ip
destination.nat.port	Port the source session is translated to by NAT Device. Typically used with load balancers, firewalls, or routers.	long
destination.port	Port of the destination.	long
dns.header_flags	Array of 2 letter DNS header flags. Expected values are: AA, TC, RD, RA, AD, CD, DO.	keyword
dns.question.class	The class of records being queried.	keyword
dns.question.name	The name being queried. If the name field contains non-printable characters (below 32 or above 126), those characters should be represented as escaped base 10 integers (\DDD). Back slashes and quotes should be escaped. Tabs, carriage returns, and line feeds should be converted to \t, \r, and \n respectively.	keyword
dns.question.type	The type of record being queried.	keyword
dns.response_code
ecs.version	ECS version this event conforms to. `ecs.version` is a required field and must exist in all events. When querying across multiple indices -- which may conform to slightly different ECS versions -- this field lets integrations adjust to the schema version of the events.	keyword
event.action	The action captured by the event. This describes the information in the event. It is more specific than `event.category`. Examples are `group-add`, `process-started`, `file-created`. The value is normally defined by the implementer.	keyword
event.category	This is one of four ECS Categorization Fields, and indicates the second level in the ECS category hierarchy. `event.category` represents the "big buckets" of ECS categories. For example, filtering on `event.category:process` yields all events relating to process activity. This field is closely related to `event.type`, which is used as a subcategory. This field is an array. This will allow proper categorization of some events that fall in multiple categories.	keyword
event.created	event.created contains the date/time when the event was first read by an agent, or by your pipeline. This field is distinct from @timestamp in that @timestamp typically contain the time extracted from the original event. In most situations, these two timestamps will be slightly different. The difference can be used to calculate the delay between your source generating an event, and the time when your agent first processed it. This can be used to monitor your agent's or pipeline's ability to keep up with your event source. In case the two timestamps are identical, @timestamp should be used.	date
event.dataset	Event dataset	constant_keyword
event.duration	Duration of the event in nanoseconds. If event.start and event.end are known this value should be the difference between the end and start time.	long
event.id	Unique ID to describe the event.	keyword
event.ingested	Timestamp when an event arrived in the central data store. This is different from `@timestamp`, which is when the event originally occurred. It's also different from `event.created`, which is meant to capture the first time an agent saw the event. In normal conditions, assuming no tampering, the timestamps should chronologically look like this: `@timestamp` < `event.created` < `event.ingested`.	date
event.kind	This is one of four ECS Categorization Fields, and indicates the highest level in the ECS category hierarchy. `event.kind` gives high-level information about what type of information the event contains, without being specific to the contents of the event. For example, values of this field distinguish alert events from metric events. The value of this field can be used to inform how these kinds of events should be handled. They may warrant different retention, different access control, it may also help understand whether the data coming in at a regular interval or not.	keyword
event.module	Event module	constant_keyword
event.type	This is one of four ECS Categorization Fields, and indicates the third level in the ECS category hierarchy. `event.type` represents a categorization "sub-bucket" that, when used along with the `event.category` field values, enables filtering events down to a level appropriate for single visualization. This field is an array. This will allow proper categorization of some events that fall in multiple event types.	keyword
geo.city_name	City name.	keyword
geo.continent_name	Name of the continent.	keyword
geo.country_iso_code	Country ISO code.	keyword
geo.country_name	Country name.	keyword
geo.location	Longitude and latitude.	geo_point
geo.name	User-defined description of a location, at the level of granularity they care about. Could be the name of their data centers, the floor number, if this describes a local physical entity, city names. Not typically used in automated geolocation.	keyword
geo.region_iso_code	Region ISO code.	keyword
geo.region_name	Region name.	keyword
log.level	Original log level of the log event. If the source of the event provides a log level or textual severity, this is the one that goes in `log.level`. If your source doesn't specify one, you may put your event transport's severity here (e.g. Syslog severity). Some examples are `warn`, `err`, `i`, `informational`.	keyword
message	For log events the message field contains the log message, optimized for viewing in a log viewer. For structured logs without an original message field, other fields can be concatenated to form a human-readable summary of the event. If multiple messages exist, they can be combined into one message.	match_only_text
network.iana_number	IANA Protocol Number (https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml). Standardized list of protocols. This aligns well with NetFlow and sFlow related logs which use the IANA Protocol Number.	keyword
network.protocol	In the OSI Model this would be the Application Layer protocol. For example, `http`, `dns`, or `ssh`. The field value must be normalized to lowercase for querying.	keyword
network.transport	Same as network.iana_number, but instead using the Keyword name of the transport layer (udp, tcp, ipv6-icmp, etc.) The field value must be normalized to lowercase for querying.	keyword
observer.name	Custom name of the observer. This is a name that can be given to an observer. This can be helpful for example if multiple firewalls of the same model are used in an organization. If no custom name is needed, the field can be left empty.	keyword
observer.product	The product name of the observer.	keyword
observer.type	The type of the observer the data is coming from. There is no predefined list of observer types. Some examples are `forwarder`, `firewall`, `ids`, `ips`, `proxy`, `poller`, `sensor`, `APM server`.	keyword
observer.vendor	Vendor name of the observer.	keyword
related.hosts	All hostnames or other host identifiers seen on your event. Example identifiers include FQDNs, domain names, workstation names, or aliases.	keyword
related.ip	All of the IPs seen on your event.	ip
related.user	All the user names or other user identifiers seen on the event.	keyword
rule.category	A categorization value keyword used by the entity using the rule for detection of this event.	keyword
rule.id	A rule ID that is unique within the scope of an agent, observer, or other entity using the rule for detection of this event.	keyword
rule.name	The name of the rule or signature generating the event.	keyword
rule.ruleset	Name of the ruleset, policy, group, or parent category in which the rule used to generate this event is a member.	keyword
source.address	Some event source addresses are defined ambiguously. The event will sometimes list an IP, a domain or a unix socket. You should always store the raw address in the `.address` field. Then it should be duplicated to `.ip` or `.domain`, depending on which one it is.	keyword
source.as.number	Unique number allocated to the autonomous system. The autonomous system number (ASN) uniquely identifies each network on the Internet.	long
source.as.organization.name	Organization name.	keyword
source.as.organization.name.text	Multi-field of `source.as.organization.name`.	match_only_text
source.bytes	Bytes sent from the source to the destination.	long
source.geo.city_name	City name.	keyword
source.geo.continent_name	Name of the continent.	keyword
source.geo.country_iso_code	Country ISO code.	keyword
source.geo.country_name	Country name.	keyword
source.geo.location	Longitude and latitude.	geo_point
source.geo.name	User-defined description of a location, at the level of granularity they care about. Could be the name of their data centers, the floor number, if this describes a local physical entity, city names. Not typically used in automated geolocation.	keyword
source.geo.region_iso_code	Region ISO code.	keyword
source.geo.region_name	Region name.	keyword
source.ip	IP address of the source (IPv4 or IPv6).	ip
source.port	Port of the source.	long
tags	List of keywords used to tag each event.	keyword
url.original	Unmodified original url as seen in the event source. Note that in network monitoring, the observed URL may be a full URL, whereas in access logs, the URL is often just represented as a path. This field is meant to represent the URL as it was observed, complete or not.	wildcard
url.original.text	Multi-field of `url.original`.	match_only_text

Changelog

Version	Details	Kibana version(s)
1.9.1	Bug fix View pull request Set field type to password on secret fields	8.12.0 or higher
1.9.0	Enhancement View pull request Add support for integration secrets	8.12.0 or higher
1.8.3	Enhancement View pull request Add caller_ip_address field in pipeline for Azure sign-in logs.	8.8.0 or higher
1.8.2	Enhancement View pull request Update Azure logs documentation.	8.8.0 or higher
1.8.1	Enhancement View pull request Update AD Logs documentation.	8.8.0 or higher
1.8.0	Enhancement View pull request Allow rerouting of Azure logs events to a different data stream.	8.8.0 or higher
1.7.0	Enhancement View pull request Rebrand Azure Spring Cloud Logs to Azure Spring Apps	8.6.0 or higher
1.6.0	Enhancement View pull request Update the package format_version to 3.0.0.	8.6.0 or higher
1.5.33	Bug fix View pull request Handle `json.properties.clientIp` as an alias of `json.properties.clientIP` in application gateway logs	8.6.0 or higher
1.5.32	Bug fix View pull request Fix mappings for `azure.activitylogs.claims.*`.	8.6.0 or higher
1.5.31	Enhancement View pull request Migration of Azure AD Identity Protection dashboard to Lens.	8.6.0 or higher
1.5.30	Enhancement View pull request Migration of Azure AD Provisioning Logs dashboard to Lens.	8.6.0 or higher
1.5.29	Enhancement View pull request Fix Azure dashboards descriptions and titles.	8.6.0 or higher
1.5.28	Enhancement View pull request Migration Alerts Overview dashboard to Lens	8.6.0 or higher
1.5.27	Bug fix View pull request Fix in Firewall dashboards	8.6.0 or higher
1.5.26	Bug fix View pull request Handle duplicate user_agent.original field in signinlogs logs	8.6.0 or higher
1.5.25	Bug fix View pull request Handle duplicate url.path field in application gateway logs	8.6.0 or higher
1.5.24	Bug fix View pull request Handle firewall events for DNAT'ed requests with attributes	8.6.0 or higher
1.5.23	Enhancement View pull request Update Azure Logs screenshot	8.6.0 or higher
1.5.22	Enhancement View pull request Migration of Azure Cloud Overview dashboard to Lens and style changes	8.6.0 or higher
1.5.21	Enhancement View pull request Migration of User Activity Dashboard to Lens	8.6.0 or higher
1.5.20	Enhancement View pull request Integration settings UI for sanitization	8.6.0 or higher
1.5.17	Enhancement View pull request Migration of Spring Cloud Overview dashboard to Lens	8.6.0 or higher
1.5.16	Enhancement View pull request Migration of Azure Spring Cloud Logs Application Cloud Logs dashboard to Lens	8.6.0 or higher
1.5.15	Enhancement View pull request Migration of Spring Cloud System Logs dashboard to Lens	8.6.0 or higher
1.5.14	Enhancement View pull request Enhancement/Improving performance of the dashboards	8.6.0 or higher
1.5.13	Enhancement View pull request Extend the Storage Account container documentation and add link to requiements and setup instructions	7.16.0 or higher 8.0.0 or higher
1.5.12	Enhancement View pull request Added categories and/or subcategories.	7.16.0 or higher 8.0.0 or higher
1.5.11	Enhancement View pull request Add a new message format to the AzureFirewallNetworkRule log category	7.16.0 or higher 8.0.0 or higher
1.5.10	Bug fix View pull request Check for 'event.original' already existing in Application Gateway and Event Hub ingest pipelines	7.16.0 or higher 8.0.0 or higher
1.5.9	Bug fix View pull request Check for 'event.original' already existing in firewall logs ingest pipeline	7.16.0 or higher 8.0.0 or higher
1.5.8	Bug fix View pull request Add `storage_account_container` option to the Application Gateway integration	7.16.0 or higher 8.0.0 or higher
1.5.7	Bug fix View pull request Fix parsing of authentication_processing_details field in signin logs	7.16.0 or higher 8.0.0 or higher
1.5.6	Bug fix View pull request Fix parsing error client port is blank and adjust for timeStamp	7.16.0 or higher 8.0.0 or higher
1.5.5	Bug fix View pull request Rename identity as identity_name when the value is a string	7.16.0 or higher 8.0.0 or higher
1.5.4	Enhancement View pull request Enable Event Hub integration by default and improve documentation	7.16.0 or higher 8.0.0 or higher
1.5.3	Enhancement View pull request Data streams start as disabled on new installs	7.16.0 or higher 8.0.0 or higher
1.5.2	Bug fix View pull request Fix PR link in changelog	7.16.0 or higher 8.0.0 or higher
1.5.1	Bug fix View pull request Fix documentations formatting (remove extra 'Overview' heading)	7.16.0 or higher 8.0.0 or higher
1.5.0	Enhancement View pull request Add Azure Application Gatewaty data stream	7.16.0 or higher 8.0.0 or higher
1.4.1	Enhancement View pull request Update Azure Logs documentation	7.16.0 or higher 8.0.0 or higher
1.4.0	Enhancement View pull request Add two new data streams to the Azure AD logs integration: Azure Identity Protection logs and Provisioning logs	7.16.0 or higher 8.0.0 or higher
1.3.0	Enhancement View pull request Add the possibility to override the default generated storage account container	7.16.0 or higher 8.0.0 or higher
1.2.3	Enhancement View pull request Update docs with recommended Event Hub configuration	7.16.0 or higher 8.0.0 or higher
1.2.2	Enhancement View pull request Update package name and description to align with standard wording	7.16.0 or higher 8.0.0 or higher
1.2.1	Bug fix View pull request Fix Azure Sign-in logs ingest pipeline bug	7.16.0 or higher 8.0.0 or higher
1.2.0	Enhancement View pull request Support Azure firewall logs	—
1.1.11	Bug fix View pull request Improve support for event.original field from upstream forwarders.	—
1.1.10	Enhancement View pull request Update readme with links to Microsoft documentation	7.16.0 or higher 8.0.0 or higher
1.1.9	Bug fix View pull request Improve handling of IPv6 IP addresses.	—
1.1.8	Enhancement View pull request Update docs with details about Event Hub name recommendations	7.16.0 or higher 8.0.0 or higher
1.1.7	Bug fix View pull request Add geo.name and result_description fields in platformlogs	7.16.0 or higher 8.0.0 or higher
1.1.6	Bug fix View pull request Fix azure.activitylogs.identity with a a concrete value Bug fix View pull request Add identity_name, tenant_id, level and operation_version into activity logs	7.16.0 or higher 8.0.0 or higher
1.1.5	Enhancement View pull request Add documentation for multi-fields	—
1.1.4	Bug fix View pull request Fix `event.duration` field mapping conflict in all Azure data streams.	—
1.1.3	Enhancement View pull request Added the `forwarded` tag by default to all log types.	—
1.1.2	Bug fix View pull request Add device_detail.is_compliant and device_detail.is_managed fields Bug fix View pull request Change authentication_requirement_policies to flattened type	7.16.0 or higher 8.0.0 or higher
1.1.1	Bug fix View pull request Fix field mapping conflict in the auditlogs data stream for `client.ip`. Changed `azure-eventhub.offset` and `azure-eventhub.sequence_number` to longs from keyword in the eventhub data stream.	—
1.1.0	Enhancement View pull request Support new Azure audit logs and signin logs	—
1.0.1	Enhancement View pull request Remove beta release tag from data streams	7.16.0 or higher 8.0.0 or higher
1.0.0	Enhancement View pull request Move azure package to GA	7.16.0 or higher 8.0.0 or higher
0.12.3	Enhancement View pull request Update to ECS 8.0	—
0.12.2	Bug fix View pull request Regenerate test files using the new GeoIP database	—
0.12.1	Bug fix View pull request Change test public IPs to the supported subset	—
0.12.0	Enhancement View pull request Release azure package for v8.0.0	—
0.11.0	Enhancement View pull request Add Azure Event Hub Input	—
0.10.1	Enhancement View pull request Uniform with guidelines	—
0.10.0	Enhancement View pull request signinlogs - Add support for ManagedIdentitySignInLogs, NonInteractiveUserSignInLogs, and ServicePrincipalSignInLogs.	—
0.9.2	Bug fix View pull request Prevent pipeline script error	—
0.9.1	Bug fix View pull request Fix logic that checks for the 'forwarded' tag	—
0.9.0	Enhancement View pull request Update to ECS 1.12.0	—
0.8.6	Bug fix View pull request Add ECS `client.ip` mapping	—
0.8.5	Enhancement View pull request Update docs and logo	—
0.8.4	Enhancement View pull request Convert to generated ECS fields	—
0.8.3	Enhancement View pull request Import geo_points from ECS	—
0.8.2	Enhancement View pull request Update error message	—
0.8.1	Enhancement View pull request Add support for springcloud logs inside the platformlogs pipeline	—
0.8.0	Enhancement View pull request Import ECS field definitions	—
0.7.0	Enhancement View pull request Add spring cloud logs	—
0.6.2	Enhancement View pull request update to ECS 1.11.0	—
0.6.1	Enhancement View pull request Escape special characters in docs	—
0.6.0	Enhancement View pull request Update integration description	—
0.5.1	Enhancement View pull request Re-add pipeline changes for invalid json	—
0.5.0	Enhancement View pull request Add input groups	—
0.4.0	Enhancement View pull request Set "event.module" and "event.dataset"	—
0.3.1	Enhancement View pull request sync package with module changes	—
0.3.0	Enhancement View pull request update to ECS 1.10.0 and adding event.original options	—
0.2.3	Enhancement View pull request update to ECS 1.9.0	—
0.2.2	Bug fix View pull request Correct sample event file.	—
0.2.1	Bug fix View pull request Add check for empty configuration options.	—
0.2.0	Enhancement View pull request Add changes to use ECS 1.8 fields.	—
0.0.1	Enhancement View pull request initial release	—

On this page

Article navigation

Requirements and setup

Settings

Logs

firewall_logs

Changelog