-
Notifications
You must be signed in to change notification settings - Fork 456
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
Container logs integration #3163
Comments
I look the document about filebeat and fleet integrations. |
Any reason why we wouldn't want both? From a discoverability angle, I do think users are going to look for this in the Docker package and may be confused why logs aren't supported if they don't see it there. |
Hey @BobDu! Sorry for the late replay here, this slipped from my notice (was on vacation that time of your post, sorry). Fair point @joshdover! From that perspective it is better to have a dedicated data_stream under each of the target environments (docker, k8s etc). We can extend https://github.com/elastic/integrations/tree/main/packages/docker by using the https://github.com/elastic/elastic-agent/tree/main/internal/pkg/composable/providers/docker provider. Quite similarly to what we do with the k8s provider. @gizas @mlunadia what do you think about prioritizing this? It seems to be a low hanging fruit. |
So I see 2 parts here:
|
@gizas since we have addressed both parts, shall we close this issue? |
@gizas I'm gonna close this now. Feel free to re-open if there is anything we missed here. |
At the moment we don't have a dedicated integration for container logs similar to what we have for the kubernetes' container logs.
It would be nice to have a dedicated package for it. It can be either a container generic one or it can be a new datastream under docker package. I think having a generic one for all types of containers would be preferable.
The text was updated successfully, but these errors were encountered: