elasticsearch

Elasticsearch Version

8.1.1

Installed Plugins

None

Java Version

bundled

OS Version

macos

Problem Description

Create a custom analyzer using below request, Note foo as an param to analyzer with bar value.

PUT customanlyzerindex
{
    "settings": {
        "analysis": {
            "analyzer": {
                "my_analyzer": {
                   

What happened:
Following the instructions on this page, I configure my alert with severity and component tags. I then configured PagerDuty side. However, the notification that I got in PagerDuty didn't include the correct field values. Specifically, the component
and severity fields wer

Kibana version: 8.3.0 snapshot

Elasticsearch version: 8.3.0 snapshot

Server OS version: darwin_x86_64

Browser version: chrome latest

Browser OS version: OS X

Original install method (e.g. download page, yum, from source, etc.): from staging

Describe the bug: When user clicks on learn about field types in discover help on field types- elastic docs open

The generic Windows audit log config lacks many event ids, e.g.

• registry events
• driver load service addition events, System/7045 and Security/4697
• likely others

As suggested in the ESM guidelines of Node.js it would be good to explicit the type of the module.

{
+  "type": "commonjs",
}