gotty VS vector

gotty + lnav

My bootstrap script ends in launching AutoGPT with GoTTY https://github.com/sorenisanerd/gotty

Setup GoTTY and allow it to run a single script only that will restart VPS. Assign password to GoTTY and give it to only trusted people to use. No need for them to install anything since GoTTY is basically "terminal in browser"

First, I suggest you to use forked GoTTY version since original one in your post wasn't updated for more than 6 years.

GoTTY. You dont need to know Golang, just download binary from release section for your platform

Honestly graylog/loki is only worth it if you want to have automatic processing/stats generation/graphing and complex log management rules. If you just want to read logs in a web interface I suggest either frontail (very basic, a bit too much for my taste) or lnav (I use this 99% of the time, over SSH) + gotty to access a terminal/lnav from a web browser - be careful to secure it properly as it basically gives shell access to your server.

Write a script(s) (docker container plex restart) that you will allow to run via web and point to it gotty, so users will run it as they are in terminal. (Just don't forget to set GOTTY_CREDENTIAL on an exposed link).

I created a custom image from https://github.com/sorenisanerd/gotty with lnav in order to view application logs in a browser. The Dockerfile and docker compose I used are below. I created symbolic links to the apps I am interested in into a single directory and mounted it to /docker/logs in the container. Thought I would share if someone else is looking for a lightweight solution to consolidate and view logs in a browser.

Having trouble with ssh? No problem, browser is all what people need, just run GoTTY and get full (or read only) access to any terminal in multiple tabs in web browser, as much as you need.

sorenisanerd/gotty: Share your terminal as a web application

I am thinking about using https://vector.dev/ but would also love opinions on the best deal for lower or reasonable cost storage/querying of logs. Thanks!

job "vector" { datacenters = ["dc1"] # system job, runs on all nodes type = "system" group "vector" { count = 1 network { port "api" { to = 8686 } } ephemeral_disk { size = 500 sticky = true } task "vector" { driver = "docker" config { image = "timberio/vector:0.30.0-debian" ports = ["api"] volumes = ["/var/run/docker.sock:/var/run/docker.sock"] } env { VECTOR_CONFIG = "local/vector.toml" VECTOR_REQUIRE_HEALTHY = "false" } resources { cpu = 100 # 100 MHz memory = 100 # 100MB } # template with Vector's configuration template { destination = "local/vector.toml" change_mode = "signal" change_signal = "SIGHUP" # overriding the delimiters to [[ ]] to avoid conflicts with Vector's native templating, which also uses {{ }} left_delimiter = "[[" right_delimiter = "]]" data=<

we are doing something similar with OTEL but we are looking at using https://vector.dev/

We don't pull logs, we forward logs to a centralized logging service.

opensearch - amazon fork of Elasticsearch https://opensearch.org/docs/latestif you do this an have distributed log sources you'd use logstash for, bin off logstash and use vector (https://vector.dev/) its better out of the box for SaaS stuff.

I have done something similar in the past: you can send the logs through a centralized syslog servers (I suggest syslog-ng) and from there ingest into ELK. For parsing I am advice to use something like Vector, is a lot more faster than logstash. When you have your logs ingested correctly, you can create your own dashboard in Kibana. If this fit your requirements, no need to install nginx (unless you want to use as reverse proxy for Kibana), php and mysql.

I think there's nothing currently that combines both logging and metrics into one easy package and visualizes it, but it's also something I would love to have.

Vector[1] would work as the agent, being able to collect both logs and metrics. But the issue would then be storing it. I'm assuming the Elastic Stack might now be able to do both, but it's just to heavy to deal with in a small setup.

A couple of months ago I took a brief look at that when setting up logging for my own homelab (https://pv.wtf/posts/logging-and-the-homelab). Mostly looking at the memory usage to fit it on my synology. Quickwit[2] and Log-Store[3] both come with built in web interfaces that reduce the need for grafana, but neither of them do metrics.

- [1] https://vector.dev

Log to stdout/stderr and collect your logs with a tool like vector (vector.dev) and send it to something like Grafana Loki.