Feature request: Visualising multiple logs in the same dashboard

[Khaaz]

Hello,
I just discovered this product and it seems like a very cool idea.

My main "real life" scenario is that I have logs from different services (in console or in text file) and I would love to be able to visualise them all in one place.

That's the use case for datadog or other visualisation tool like that for production. But for local environment, it would be super convenient to have juste one dashboard and all the logs there.

Is there any way to do that right now? Or any plan to support it in the future?

[soorajshankar]

Is there any way to do that right now? Or any plan to support it in the future?
Interesting! It's not possible at the moment, but It should be easy to implement - I'll give it a shot soon.

BTW could you explain a little bit on what kind of services are you trying to see? like any sample of logs (hiding all sensitive info) which comes from different services? Asking this to understand if there is a common pattern so that we can build a few ways to better read the logs- may be a set of separators or parsers for the better reading, filtering, processing etc.

[Khaaz]

If i'm speaking about my ideal "simple" visualisation tool. I would want

• tab per "service" (or per logfile or whatever), that just shows plain logs (with maybe options for searching but doesn't have to be too much)
• global tab with some filtering.
  • check / uncheck the service you want to be displayed
  • each log shows which service it's from
  • way to filter, do search and aggregation:
    • requestId
    • correlationId
    • userId
    • groupId

For the way my logs are structured right now, it's not necessary optimum for correct visualisation in tools like that so i'll probably do more work on the structure later.
But as far as I can tell various way of filtering are:

• log plain json object
• key=value format
• logs with separators like : ; | /

Here some examples of my logs right now (again, I don't think they are "ideal" logs, pretty sure it would be pretty sure for tools like datadog and other log aggregators):

For example:

I basically log IN and OUT bound request, with headers and request content/body;

An option to hide part of the log (like you have a key data that you can hide or not) could also be a cool addition