GKE Stackdriver UI: Only showing stdout events about nodejs-logging-bunyan HOT 12 CLOSED

@dieguezz working on a release in #131. Hopefully it can be shipped soon.

from nodejs-logging-bunyan.

@dieguezz those are all logs parsed from stdout. The stream sent by loggingBunyan.stream() are supposed to show up under a different category in the UI.

I am trying out LoggingBunyan on my own GKE app, and I can reproduce the actual issue that the logs don't seem to be available anywhere in the Logging UI.

I'm investigating this – stay tuned.

from nodejs-logging-bunyan.

The fix has been released in v0.9.1: https://www.npmjs.com/package/@google-cloud/logging-bunyan?activeTab=versions. @dieguezz please give it a shot and let us know if this works better.

from nodejs-logging-bunyan.

Hi @dieguezz. I see that you have a stdout stream in addition to the LoggingBunyan stream. For code running on some Google Cloud environments such as GAE and GKE, the stdout is captured by default and sent to Stackdriver Logging (albeit in an unstructured way – since stdout is unstructured) in addition to the stream that LoggingBunyan sends.

Are you looking at the stdout or the bunyan log in the Stackdriver Logging user interface?

from nodejs-logging-bunyan.

Hey @ofrobots, my code is running on GKE and i am looking at (screenshot) the Stackdriver Logging ui. I am doing different test but i don't find the combination.

I think that default behavior is as you say, they print everything from stdout as info and everyhting from stderr as error, but i want to differ warnings, debug, info, and well, all levels.

If i remove the stdout stream and leave the LoggingBunyan, i am not receiving anything in Stackdriver logging ui. Can you show me an example of how should i configure it?

from nodejs-logging-bunyan.

For an AppEngine (GAE) app, here's an example of where the log would shows up:

Let me see how this would show up in a GKE environment.

from nodejs-logging-bunyan.

You mean this?

Anyway, all of them appear as info unless i add severity like: logger.info({ severity: 'LEVEL', ... }), but that should be done automatically from level as stated in related issue
Then appears as should:

from nodejs-logging-bunyan.

@dieguezz Can you try selecting "All namespace_id" when navigating the logs?

Then you can further filter out the log to see only the bunyan logs:

Sorry that this is complicated and non-obvious. We will get this improved.

Notes for my fellow maintainers of this repo: The root cause is that this library is sending LogEntries without a namespace_id specified in the container monitored resource descriptor on GKE. The Logging UI expects this field to be non-empty. The problem is that the value of namespace_id is easily available inside a container – or at least, I don't know the mechanism to get the value. This needs to be investigated and fixed.

from nodejs-logging-bunyan.

You are right, i see them when i select all. Any ideas of why is this? i'd like to do it selecting just the branch i want (only one namespace)

from nodejs-logging-bunyan.

Implementing a fix over here: googleapis/nodejs-logging#191

from nodejs-logging-bunyan.

Thanks a lot @ofrobots, just one more thing. When are you going to deploy a new release?

from nodejs-logging-bunyan.

This fix needs to be applied to https://github.com/googleapis/nodejs-logging-winston as well as Winston is doing the same thing.

from nodejs-logging-bunyan.