Skip to content

New Integration Kiteworks Totemomail#17400

Open
WildDogOne wants to merge 32 commits intoelastic:mainfrom
WildDogOne:totemo-mail
Open

New Integration Kiteworks Totemomail#17400
WildDogOne wants to merge 32 commits intoelastic:mainfrom
WildDogOne:totemo-mail

Conversation

@WildDogOne
Copy link
Contributor

@WildDogOne WildDogOne commented Feb 12, 2026

New Integration Kiteworks Totemomail

Integration for the Kiteworks Totemomail Service.
Totemomail is a Securemail service used for encrypted and or signed mail traffic between organisations and users.
The goal of the integration is that Mailflow through the service can be traced correctly.
Additionally I want to make sure that Debug logs are extracted to help troubleshooting the service if needed.

Checklist

  • I have added an entry to my package's changelog.yml file.
  • I have verified that all data streams collect metrics or logs.

Author's Checklist

  • Evaluate if a variable to choose which logtypes are ingested makes sense (debug/info)
  • Fix Build Error: ingest_pipeline/default.yml" is invalid: field processors.16.remove: if is required
  • Fix Build Error: ingest_pipeline/default.yml" is invalid: field processors.16.remove.field: rename "message" to "event.original" processor requires remove "message" processor (JSE00001)

How to test this PR locally

Logs are included in the pull requests

@WildDogOne WildDogOne requested a review from a team as a code owner February 12, 2026 16:20
@WildDogOne
Copy link
Contributor Author

I want to ask if it would make sense to have a flag for choosing which logs the organisation wants to ingest, just informational logs or debug logs as well.

Of course an organisation could always make a custom pipeline to drop debug logs, but maybe this is a feature people would enjoy?

@andrewkroh andrewkroh added New Integration Issue or pull request for creating a new integration package. documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. labels Feb 12, 2026
@github-actions
Copy link
Contributor

Vale Linting Results

Summary: 2 warnings, 2 suggestions found

⚠️ Warnings (2)
File Line Rule Message
packages/totemo/_dev/build/docs/README.md 19 Elastic.DontUse Don't use 'very'.
packages/totemo/docs/README.md 19 Elastic.DontUse Don't use 'very'.
💡 Suggestions (2)
File Line Rule Message
packages/totemo/_dev/build/docs/README.md 19 Elastic.Wordiness Consider using 'because' instead of 'Since'.
packages/totemo/docs/README.md 19 Elastic.Wordiness Consider using 'because' instead of 'Since'.

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. New Integration Issue or pull request for creating a new integration package.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants