I haven't found a good solution that works well with fly.io (whose own monitoring is meh). Logtail just doesn't work well; logz.io have their heads up their asses; dd and nr are too expensive. If you can get a first class integration going with fly, that'd be huge.
Also please make sure you have multi-line logs covered out of the gate. (Logtail, for example, doesn't support multiline stacktraces(!))
One thing that isn't clear to me from your marketing is what capability you have to support frameworks that aren't in your list. Do you have a regexp/generic parsing engine/ui?
What could fly.io be doing better here? (There's a threshold past which we'd say you should be using Highlight.io or Sentry, I'm just curious what the nuts-and-bolts things we're missing are).
> Also please make sure you have multi-line logs covered out of the gate. (Logtail, for example, doesn't support multiline stacktraces(!))
Noted. We're doing a push on our logging UX soon and can take a look.
> One thing that isn't clear to me from your marketing is what capability you have to support frameworks that aren't in your list. Do you have a regexp/generic parsing engine/ui?
I'm not entirely sure about the question, but we can receive logs via several specifications. OTEL, HTTP, Fluentbit, etc.. Does that answer your question? Or are you talking more about log filtering (i.e. filtering out logs for a specific log level)?
Also please make sure you have multi-line logs covered out of the gate. (Logtail, for example, doesn't support multiline stacktraces(!))
One thing that isn't clear to me from your marketing is what capability you have to support frameworks that aren't in your list. Do you have a regexp/generic parsing engine/ui?