You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
epr.elastic.co is essential for integrations to be identified by Kibana and work properly. In air-gapped environments, Kibana is not able to reach this endpoint and that makes adoption of the fleet for such customers challenging. We have an experimental version of the self-managed EPR that customers could host in their network and easily use agent integrations. We wish to open that for customers. We have been using it internally for development and the only thing that is required for this capability at the moment is documentation. Once we have the documentation, it will be easier for users to discover this capability and use it which will, in turn, help us in gathering feedback and planning for future iterations.
We already have the content and looking for a place to host it. Integrations developer guide would seem to fit the requirement. Hence, adding a separate section for Package Registry or a sub-section under Package Specification in the Integrations developer guide would be great.
Collaboration
The prodiuct team will provide the initial content
Description
epr.elastic.co is essential for integrations to be identified by Kibana and work properly. In air-gapped environments, Kibana is not able to reach this endpoint and that makes adoption of the fleet for such customers challenging. We have an experimental version of the self-managed EPR that customers could host in their network and easily use agent integrations. We wish to open that for customers. We have been using it internally for development and the only thing that is required for this capability at the moment is documentation. Once we have the documentation, it will be easier for users to discover this capability and use it which will, in turn, help us in gathering feedback and planning for future iterations.
We already have the content and looking for a place to host it. Integrations developer guide would seem to fit the requirement. Hence, adding a separate section for Package Registry or a sub-section under Package Specification in the Integrations developer guide would be great.
Collaboration
Suggested Target Release
7.15
Stakeholders
@mukeshelastic , @sorantis, @mtojek, @masci
The text was updated successfully, but these errors were encountered: