-
Notifications
You must be signed in to change notification settings - Fork 6
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
[FEAT] Log Aggregation #68
Comments
The license for Sentry appears to be modified Apache, so would have to evaluate if that is compatible and acceptable for our use. Open Telemetry is Apache 2.0 licensed and may also be applicable for metrics reporting in addition to logging Graylog uses the same license as MongoDb apparently which I believe we have already evaluated as acceptable for our use cases. |
Allure was also mentioned but I have not researched that implementation |
Official docs for Kubernetes outline some different architecture options. It seems a node logging agent might be the easiest to implement as it requires no changes to containers and only adds one container per node vs a sidecar container per pod. I believe all of the logging we care about is already using ovos-utils.log so formatting is uniform and log names can be parsed in the logging backend |
From @mikejgray this article outlines some good background information on logging. For the moment, Longer-term we may want to use sidecar containers to build structured logs and implement proper aggregation on a dedicated pod |
As discussed, we will get an account opened with Sentry for @NeonKirill to integrate with Klat to start. If this works well, we can extend other services to support this and work it into the |
Closed by #80 |
Objective
Currently, many services interact with each other, so viewing synchronized logs is sometimes necessary. Additionally, we have no documented tools for viewing container logs in k8s (k9s is not really a log viewer).
Initial Implementation Requirements
Other Considerations
The text was updated successfully, but these errors were encountered: