Skip to content

Research: Investigate Runing ELK on Fly.io #2

@nelsonic

Description

@nelsonic

Context

At present the Fly.io logging is very basic. e.g: https://fly.io/apps/authprod/monitoring
image

This is "OK" for basic debugging/diagnosing but it's useless for trend analysis as there's no clarity on log retention and there's no ability to search, etc.

If you read the flyctl logs docs: https://fly.io/docs/flyctl/logs they are basic - at the time of writing ...
image

Presumably not many people are needing anything advanced.
or the people that need something more advanced are using a 3rd party service. 🤷‍♂️

There's nothing like CloudWatch aws.amazon.com/cloudwatch

Todo

Confirm resource requirements, this is a JAVA beast after all ... https://github.com/elastic 🙄

image

Can we run a Single Docker Container?

https://elk-docker.readthedocs.io/

Read: https://medium.com/@svetob/sending-elixir-logs-to-logstash-as-json-1396605f9b7b
and https://github.com/svetob/logstash-json

Metadata

Metadata

Assignees

Labels

enhancementNew feature or enhancement of existing functionalitygood first issueGood for newcomershelp wantedIf you can help make progress with this issue, please comment!

Type

No type

Projects

Status

✅ Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions