Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem?

I want to enhance monitoring for a process captured by Tetragon by looking at the environment variables available to the captured process.

Describe the feature you would like

To further enhance observability within a process's context, this feature will allow specified environment variables to be exported alongside other metadata when an event is captured. Such that, when specifying a Tetragon event, you can specify which environment variables you want to export when a Tetragon event is captured. For example:

kprobes:
- call: <some_call_here>
  env: ["ENV1", "ENV2"]

would yield the following entry in the json logs:

{
  "env": {
      "ENV1": "<some_string_value_here>",
      "ENV2:  "<some_string_value_here>"
  }
}

Describe your proposed solution

No response

Code of Conduct

• I agree to follow this project's Code of Conduct