You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm investigating options for client-side logging being sent to Stackdriver so it lives along side our server-side logging. This seemed to be the only option that had some backing which is why I was asking. Thanks for digging in internally with the team!
No update. It is likely that this library will stay an "unofficial Google product" and will stay maintained on the side by volunteers like me and whoever sends PRs to this repo.
The code is very simple (200 lines), so any business that wants to depend on it could do a code review to decide if they want to proceed. The library is also easy to re-implement, as it is basically a thin wrapper on top of the Error Reporting API.
This is also why I want to keep this library simple and I might push back adding non-critical features. Simplicity is a feature. Over time, the library became more complex, in term of dependencies, complexity of build step and usability (more optional settings). Keeping it simple with as less dependencies as possible is the best way to keep keep it alive.
Maybe there's no need for the comments in the code examples that say "Do not use in production environments" anymore though?
It's quite discouraging to see.
Reacted by Mike Oakley, formplus-dev, Gjermund Garaba, Alessandro, Dima Vishnevetsky, Nick Holland, Larry Johnson, Kenichiro Wakitani and Giuliano Mega
Activity
[-]Out of "experimental"[/-][+]Out of "experimental"?[/+]steren commentedon Nov 30, 2019
As far as I know, this library is not officially supported. I Can follow up internally to see if it could be.
hershmire commentedon Dec 2, 2019
I'm investigating options for client-side logging being sent to Stackdriver so it lives along side our server-side logging. This seemed to be the only option that had some backing which is why I was asking. Thanks for digging in internally with the team!
tessacrowdis commentedon Dec 18, 2019
I'm also very curious about this for similar reasons. Figure I would express my interest as well!
oskbor commentedon Feb 26, 2020
Hi @steren , any updates on if this could be officially supported?
steren commentedon Feb 27, 2020
No update. It is likely that this library will stay an "unofficial Google product" and will stay maintained on the side by volunteers like me and whoever sends PRs to this repo.
The code is very simple (200 lines), so any business that wants to depend on it could do a code review to decide if they want to proceed. The library is also easy to re-implement, as it is basically a thin wrapper on top of the Error Reporting API.
This is also why I want to keep this library simple and I might push back adding non-critical features. Simplicity is a feature. Over time, the library became more complex, in term of dependencies, complexity of build step and usability (more optional settings). Keeping it simple with as less dependencies as possible is the best way to keep keep it alive.
CC @JustinBeckwith
alkstal commentedon May 18, 2021
Maybe there's no need for the comments in the code examples that say "Do not use in production environments" anymore though?
It's quite discouraging to see.