OpenVPN Integration (1. Cloud and 2. On-premise)

[austinsonger]

Integration release checklist

This checklist is intended for integrations maintainers to ensure consistency when creating or updating a Package, Module or Dataset for an Integration.

All changes

• [ ] Change follows the contributing guidelines
• [ ] Supported versions of the monitoring target are documented
• [ ] Supported operating systems are documented (if applicable)
• [ ] Integration or System tests exist
• [ ] Documentation exists
• [ ] Fields follow ECS and naming conventions
• [ ] At least a manual test with ES / Kibana / Agent has been performed.
• [ ] Required Kibana version set to:

[SebastianHuettersen]

We need to consider further differentiations in the approach

One Integration for the cloud service, if possible. It seems there's no straightforward export option in the documentation, so we might need to explore other methods

Two Integrations for onPrem services:

• OpenVPN Community Editio
• OpenVPN Access Server

While it might be tempting to create a single integration for both, it's worth noting that this could potentially impact performance, particularly for the Community Edition. This is because the Access Server logs have a slightly different structure, and there are significantly more diverse logs to consider. The Access Server hosts multiple services and logs from these services in addition to the OpenVPN daemon.

Currently, I'm focused on developing the integration for the OpenVPN Community Edition.

• openvpn_server_ce

[botelastic[bot]]

Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!