Skip to content
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

CaptAgent vs Native HEP Agents #585

Closed
idanam-del opened this issue Apr 16, 2023 · 1 comment
Closed

CaptAgent vs Native HEP Agents #585

idanam-del opened this issue Apr 16, 2023 · 1 comment

Comments

@idanam-del
Copy link

What are the Differences between them?

I already know from opening an issue here that current version CaptAgent supports ssl encryption by default and for Native HEP Agents, it is needed to set up a stunnel.

So my question is what else?

thanks

@lmangani
Copy link
Member

Passive agents (heplify, captagent, etc) offer the HEP functionality without impacting the monitored application and they're generally more flexible, but they do NOT support tls encryption. Native agents (siptrace, res_hep, and any other native HEP client) are variable in flexibility, but they are able to report both clear and encrypted traffic without compromising security. The two can be mixed freely to achieve the desired architecture.

The transport either native or passive agent uses for HEP is agnostic to the choice and there are no stunnels required, unless one wants to deliver HEP over a secure connection to a remote collector.

Hope this answers your question.

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

No branches or pull requests

2 participants