Log raw events to a separate log file

[belimawr]

• Depends on Log raw events to a separate log file beats#38767 being merged first and new snapshot with those changes being released.

What does this PR do?

This commit introduces a new logger core, used when collecting logs from sub process, that can be configured through logging.event_data and is used to log any message that contains the whole event or could contain any sensitive data. This is accomplished by adding log.type: event to the log entry. The logger core is responsible for filtering the log entries and directing them to the correct files.

Why is it important?

Some Beats outputs will log raw event data on certain types of errors, events can contain sensitive information that should not be present in the log files. This PR address this problem by logging event data to a separate log file.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in ./changelog/fragments using the changelog tool
• I have added an integration test or an E2E test

Author's Checklist

• Update public documentation
• Update elastic-agent.reference.yml
• Implement collection of those files in the diagnostics (the whole log folder is already collected)
• Implement opt-out flag to control whether the event log file is present in the diagnostics or not
• Decide and implement how the command elastic-agent logs should handle the event log file
• Update elastic-agent-libs once [logp] Add typed loggers allowing log entries to go to different outputs elastic-agent-libs#171 is merged
• Update mock-es once Move the main package to cmd/mock-es so the API can be imported by other packages leehinman/mock-es#1 is merged
• [Rebase onto main once https://github.com/Use go install instead of go get #4672 is merged
• Wait for Log raw events to a separate log file beats#38767 to be merged and a new Beats snapshot to be published
• Manual test for the log level change

The diagnostics command

The diagnostics collect command will by default collect all events log files, there is a flag to opt out of this behaviour that can both: be passed via CLI or Fleet Action.

The logs command

The logs command can also read the events log files, it creates two streams for reading logs, one for the events logs and another for the normal logs, they share the same settings, but the line count is independent, i.e, if you set -n 10, each stream will read 10 lines.

When reading a number of lines, not in follow mode, both streams will get mixed up and the entries might not be completely ordered by time.

When in follow mode and as new lines are added, the streams will be correctly ordered.

How to test this PR locally

1. Package the Elastic-Agent
2. Replace the Filebeat binary by the binary built from Log raw events to a separate log file beats#38767
3. Create /tmp/flog.log with a few lines, the data is not important
4. Start the Elastic-Agent with the following configuration (adjust if needed)

outputs:
  default:
    type: elasticsearch
    hosts:
      - https://localhost:9200
    username: elastic
    password: changeme
    preset: balanced
    ssl.verification_mode: none

inputs:
  - type: filestream
    id: your-input-id
    streams:
      - id: your-filestream-stream-id
        data_stream:
          dataset: generic
        paths:
          - /tmp/flog.log

# Disable monitoring so there are less Beats running and less logs being generated.
agent.monitoring:
  enabled: false
  logs: false
  metrics: false
  pprof.enabled: false
  use_output: default
  http: # Needed if you already have an Elastic-Agent running on your machine
    enabled: false
    port: 7002 

agent.grpc: # Needed if you already have an Elastic-Agent running on your machine
  address: localhost
  port: 7001

# This just reduces the amount of logs.
agent.logging.metrics.enabled: false

To create ingest failures the easiest way is to close the write index from the datastream, to do that go to Kibana -> Dev Tools

To get the backing index for a datastream:

GET /_data_stream/logs-generic-default

This will return something like:

{
  "data_streams": [
    {
      "name": "logs-generic-default",
      "timestamp_field": {
        "name": "@timestamp"
      },
      "indices": [
        {
          "index_name": ".ds-logs-generic-default-2024.01.22-000001",
          "index_uuid": "0pq-XIYfSjuUQhTxlJKJjQ",
          "prefer_ilm": true,
          "ilm_policy": "logs",
          "managed_by": "Index Lifecycle Management"
        }
      ]
    }
  ]
}

Take note of the index_name .ds-logs-generic-default-2024.01.22-000001.
Close this index:

POST .ds-logs-generic-default-2024.01.22-000001/_close

5. Add more data to the file /tmp/flog.log
6. In the folder you're running the Elastic-Agent, look for a log file in data/elastic-agent-<hash>/logs/events the file name is something like elastic-agent-events-data-20240125.ndjson. You should see a log entry like this one:

{
  "log.level": "warn",
  "@timestamp": "2024-01-25T14:48:51.115+0100",
  "message": "Cannot index event publisher.Event{Content:beat.Event{Timestamp:time.Date(2024, time.January, 25, 14, 48, 46, 614819591, time.Local), Meta:{\"input_id\":\"your-input-id\",\"raw_index\":\"logs-generic-default\",\"stream_id\":\"your-filestream-stream-id\"}, Fields:{\"agent\":{\"ephemeral_id\":\"a06806a9-f18d-4ffa-bee1-debcc15f7cf5\",\"id\":\"0ff4eb46-71e1-4c49-a921-3b984b303c0f\",\"name\":\"millennium-falcon\",\"type\":\"filebeat\",\"version\":\"8.13.0\"},\"data_stream\":{\"dataset\":\"generic\",\"namespace\":\"default\",\"type\":\"logs\"},\"ecs\":{\"version\":\"8.0.0\"},\"elastic_agent\":{\"id\":\"0ff4eb46-71e1-4c49-a921-3b984b303c0f\",\"snapshot\":false,\"version\":\"8.13.0\"},\"event\":{\"dataset\":\"generic\"},\"host\":{\"architecture\":\"x86_64\",\"containerized\":false,\"hostname\":\"millennium-falcon\",\"id\":\"851f339d77174301b29e417ecb2ec6a8\",\"ip\":[\"42.42.42.42\",,\"ec8a:fc90:d347:6316:116e:8a27:f731:08ff\"],\"mac\":[\"95-A2-37-0D-71-73\",],\"name\":\"millennium-falcon\",\"os\":{\"build\":\"rolling\",\"family\":\"arch\",\"kernel\":\"6.7.0-arch3-1\",\"name\":\"Arch Linux\",\"platform\":\"arch\",\"type\":\"linux\",\"version\":\"\"}},\"input\":{\"type\":\"filestream\"},\"log\":{\"file\":{\"device_id\":\"34\",\"inode\":\"172876\",\"path\":\"/tmp/flog.log\"},\"offset\":1061765},\"message\":\"154.68.172.7 - ritchie3302 [25/Jan/2024:14:10:52 +0100] \\\"HEAD /supply-chains/metrics/platforms HTTP/1.1\\\" 502 13383\"}, Private:(*input_logfile.updateOp)(0xc000fc6d20), TimeSeries:false}, Flags:0x1, Cache:publisher.EventCache{m:mapstr.M(nil)}} (status=400): {\"type\":\"index_closed_exception\",\"reason\":\"closed\",\"index_uuid\":\"0pq-XIYfSjuUQhTxlJKJjQ\",\"index\":\".ds-logs-generic-default-2024.01.22-000001\"}, dropping event!",
  "component": {
    "binary": "filebeat",
    "dataset": "elastic_agent.filebeat",
    "id": "filestream-default",
    "type": "filestream"
  },
  "log": {
    "source": "filestream-default"
  },
  "log.origin": {
    "file.line": 461,
    "file.name": "elasticsearch/client.go",
    "function": "github.com/elastic/beats/v7/libbeat/outputs/elasticsearch.(*Client).bulkCollectPublishFails"
  },
  "log.type": "event",
  "ecs.version": "1.6.0",
  "log.logger": "elasticsearch"
}

Note the "log.type": "event" and that this log entry is not present in other log files or the logs that go to stdout/stderr.

Related issues

• Depends on Log raw events to a separate log file beats#38767
• Depends on [logp] Add typed loggers allowing log entries to go to different outputs elastic-agent-libs#171
• Blocked by Beats packing fails with Error: failed to run msiextract: exec: "msiextract": executable file not found in %PATH% (output: ) golang-crossbuild#400

## Use cases
## Screenshots
## Logs

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

---

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b event-logger-for-process upstream/event-logger-for-process
git merge upstream/main
git push upstream event-logger-for-process

[mergify]

This pull request does not have a backport label. Could you fix it @belimawr? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b event-logger-for-process upstream/event-logger-for-process
git merge upstream/main
git push upstream event-logger-for-process

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b event-logger-for-process upstream/event-logger-for-process
git merge upstream/main
git push upstream event-logger-for-process

[elasticmachine]

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

[pierrehilbert]

@bturquet could we please have someone to review here?

[elastic-sonarqube]

Quality Gate passed

Issues
6 New issues
1 Fixed issue
0 Accepted issues

Measures
0 Security Hotspots
51.1% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube