-
Notifications
You must be signed in to change notification settings - Fork 7
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
Adopt log shipping via DevX logs #789
Conversation
f137d73
to
c6fc9b7
Compare
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> | ||
<encoder class="net.logstash.logback.encoder.LogstashEncoder" /> | ||
</appender> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Logs written to stdout are collected by the journal daemon, which in turn is forwarded to Central ELK by devx-logs.
case Some(stream) => | ||
val maybeInstanceId = Try(EC2MetadataUtils.getInstanceId).toOption | ||
val loggingContext = Map( | ||
"buildId" -> prism.BuildInfo.buildNumber |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change drops this log marker.
Since adopting GuCDK's application log shipping capability, this dependency is no longer needed.
Logs written to stdout are picked up by the journal daemon. FluentBit is configured to forward journal logs to Central ELK.
c6fc9b7
to
0f21143
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Deployed to code and (successfully) checked for shippedBy
What does this change?
Adopts https://github.com/guardian/devx-logs to ship application logs to Central ELK. This change allows us to remove an application dependency (https://github.com/guardian/kinesis-logback-appender), ultimately reducing the volume of code in the repository.
How to test
DevX Logs adds a
ShippedBy
marker to each log line. Therefore, to demonstrate this is working, we can deploy and view the logs1:How can we measure success?
Fewer things to maintain in this repository.
Footnotes
The screenshot is limited to "healthcheck" logs, as other application logs contain account IDs. ↩