I’ve also had Timber support be non-responsive and am evaluating alternatives for when their libraries are abandoned. It’s a shame because I love quite a few things about their platform:
We use DataDog at my company, I’ve generally been quite happy with their logging solution, and the ability to switch back and forth between logs and metrics within the same timespan has been quite helpful.
Oh yes! I’ll do that. I want to test it out to make sure it all works correctly first, but we’ll try and do that very soon. Thanks for letting me know about this.
@chasers Thanks for making Logflare! It looks pretty great. I tried out the URL @slouchpie provided, but ran into a small problem. Logflare receives the data and displays what it received, but does not seem to parse the lines according to the format we are sending. I looked around for documentation, but couldn’t find anything that exactly fits.
We drain logs to HTTPS endpoints using the same format as Heroku, described here: Log Drains | Heroku Dev Center. In fact, we use Heroku’s logplex router to do the draining so supporting this format means you’ll support both Heroku and Gigalixir.
This is an example log line I see on Logflare.
217 <190>1 2020-08-08T16:12:15.382251+00:00 host bar bar-587b6c56bd-6j9sq - e[36mweb.1 | e[0m16:12:15.381 [warn] [libcluster:k8s_example] kubernetes strategy is selected, but :kubernetes_node_basename is not configured!
Notice the 217 <190>1, which is metadata.
Also, as a side note, would you be able to handle the ANSI control sequences, such as those surrounding web.1 | inside the logs, which change the colors? For what it’s worth, Timber displayed the colors, but I totally understand if it’s not a priority.
Let me know if we should move this discussion to a separate channel/thread. Thanks!
@jesse Yep for sure will do all this. Just added the endpoint for your / Heroku’s log drains Friday because @slouchpie wanted it. Been focused on Cloudflare & Vercel users. Had an Elixir Logger backend for a while because it’s written in Elixir but there is more interest recently from Elixir users. Anyway, I’ll ping you when this is done!
@jesse Okay the new Logplex friendly syslog parser is now live. Less than a minute from singing up for Logflare to seeing a Gigalixir log event in Logflare!
The endpoint looks like:
https://api.logflare.app/logs/logplex?api_key=YOUR_API_KEY&source=YOUR_SOURCE_ID
Here’s a run-through:
Everything is getting parsed as you’ll see. And when there is JSON in the message that gets parsed into it’s own object as well. ANSI colorizing is not there yet, but coming soon.
@slouchpie oh, please update your log drain to use /logs/logplex instead of /logs/syslog. Logplex is slightly different than the spec so we’d like to use a special endpoint for that and reserve the generic one for the exact spec.
Replying to myself for posterity: don’t use this syslog URL. instead use https://api.logflare.app/logs/logplex?api_key=YOUR_API_KEY&source=YOUR_SOURCE_ID