Skip to content

Initial discussion for email object #815

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Initial discussion for email object #815

wants to merge 1 commit into from

Conversation

dainok
Copy link

@dainok dainok commented Apr 17, 2020

I would like to start a discussion about adding an object for emails or not.
MTA logs could fit in events, but a more detailed log need a specific object.

Questions:

  • Makes sense for you? How do you translate MTA logs to ECS schema?
  • Can I define an array of objects? Examples: "to" is an array of dicts (address, full name), and attachments would be an array of files.
  • Suggested fields to add?

Feel free to comment.

@ebeahan ebeahan added the review label Jul 8, 2020
@ebeahan
Copy link
Member

ebeahan commented Jul 8, 2020

Adding email support into the schema is something many users have voiced interest in, and there's been a lot of good discussion in #411. I'd recommend also sharing any thoughts/expectations/ideas to add to the discussion there as well as those comments are extremely useful!

An addition of this scope would definitely be a great candidate for the RFC process we've recently established.

@dainok
Copy link
Author

dainok commented Jul 13, 2020

Moving to #411

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants