Allow integration with loggers (pino and other) for ability to aggregate all Keystone output in structured mode #7668
Replies: 4 comments
-
Here are example of logs from Keystone in plaintext, that good to have in JSON format:
And only in line 5 there is a custom log record, generated through a 'Pino' logger. |
Beta Was this translation helpful? Give feedback.
-
+1, very useful feature |
Beta Was this translation helpful? Give feedback.
-
A good idea. The feature will greatly facilitate the support and control of applications. |
Beta Was this translation helpful? Give feedback.
-
It is a critical feature for running Keystone in major cloud providers. We're deploying this using Google App Engine, which creates a container inside a managed instance. |
Beta Was this translation helpful? Give feedback.
-
Now Keystone simply outputs the log lines into stdout via
console.log
that makes it hard to integrate with modern logging libraries like Pino, Winston, Bunyan, npmlog, etc.To allow the integration we can simply create a middleware library
logger
, that by default just do the same thing -console.log('string')
but allow replacing it by any custom external library to give flexible log aggregation ability. What do you think about this idea?Beta Was this translation helpful? Give feedback.
All reactions