-
Notifications
You must be signed in to change notification settings - Fork 5
Stream console.log output somewhere #72
Comments
TBH Kafka or ClickHouse would be best (in practice just Kafka would do)… But that's EE only. |
The problem we're trying to solve is twofold:
Here's a rough proposal to capture/stream logs without introducing any new technologies:
Could this work and be simple enough? Or is this over-engineering? I'd like to avoid writing a new row into postgres per |
This would definitely work, though sounds kind of dirty… Lots of data handholding to ensure reasonable integrity. |
I think we should still have some basic logs on OSS as well. So I'd start with writing something very basic and if needed, we can develop a good EE logging solution after. |
From a customer slack chat, it would be great if the plugin log also contains "debug" events like "Plugin loaded", just to be reassured that everything is working as it should. In addition to that, it might be cool to keep track of how many events a plugin has operated on and show that somewhere in the interface... |
Closing since this is only awaiting deployment now. |
To improve the dev experience, running
console.log
(and.info
, etc) inside the plugin should send this information somewhere.First thoughts:
console.log = (...args) => (posthog.capture(`${pluginName} console.log`, { args })
? Too easy to endlessly loop...plugin_config
in postgres? Too high throughput...The text was updated successfully, but these errors were encountered: