Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integration with Google Cloud Platform Error Reporting #3767

Open
SethFalco opened this issue Apr 22, 2020 · 2 comments
Open

Integration with Google Cloud Platform Error Reporting #3767

SethFalco opened this issue Apr 22, 2020 · 2 comments
Labels
backlog This is not on the Weblate roadmap for now. Can be prioritized by sponsorship. enhancement Adding or requesting a new feature. good first issue Opportunity for newcoming contributors. hacktoberfest This is suitable for Hacktoberfest. Don’t try to spam. help wanted Extra attention is needed.

Comments

@SethFalco
Copy link
Contributor

SethFalco commented Apr 22, 2020

Is your feature request related to a problem? Please describe.
Currently, in Weblate I am seeing the message in Performance report:

Error collection is not configured, it is highly recommended for production use (Documentation)

Upon reading the documentation I can see the default integrations include Sentry, and Rollbar, but these are additional services one might need to sign up for, or potentially even pay for depending on usage

Describe the solution you'd like
While this is a bit petty, it'd be nice as a Google Cloud Platform user to be able to integrate cleanly with the error reporting and logging solutions provided on them.

It would be nice if there was an additional integration provided for use with Google Cloud Platforms logging and error reporting, this is especially nice for users or companies that are already using Google Cloud Platform anyway.

Additional context
It may be worth noting based on pricing, for an existing Google Cloud Platform user, it appears to work out cheaper overall to depend on Google services vs Sentry or Rollbar as well, while they also offer free tiers, there are other arbitrary limits such as members, history, number of errors, rather than gigabytes of logs. Plus GCP will allow logs in general to get piped to the online log previewer which allows server maintainers to view additional information if desired.

@nijel
Copy link
Member

nijel commented Apr 22, 2020

potentially even pay for depending on usage.

And Google Cloud Platform doesn't potentially need pay for depending on usage? This is not a fair argument. Especially since Sentry is open source and you are free to run own instance.

Still, it would be useful addition. Given that nobody of us uses GCP, it's unlikely that we will implement this, but patches are always welcome and integrating additional service should be straightforward, the code is here: https://github.com/WeblateOrg/weblate/blob/master/weblate/utils/errors.py

There is Python module for reporting: https://googleapis.dev/python/clouderrorreporting/latest/usage.html

@nijel nijel added backlog This is not on the Weblate roadmap for now. Can be prioritized by sponsorship. enhancement Adding or requesting a new feature. labels Apr 22, 2020
@github-actions
Copy link

This issue has been added to backlog. It is not scheduled on our road map, but it might be eventually implemented. In case you desperately need this feature, please consider helping or funding the development.

@nijel nijel added the help wanted Extra attention is needed. label May 19, 2020
@nijel nijel added good first issue Opportunity for newcoming contributors. hacktoberfest This is suitable for Hacktoberfest. Don’t try to spam. labels Sep 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog This is not on the Weblate roadmap for now. Can be prioritized by sponsorship. enhancement Adding or requesting a new feature. good first issue Opportunity for newcoming contributors. hacktoberfest This is suitable for Hacktoberfest. Don’t try to spam. help wanted Extra attention is needed.
Projects
None yet
Development

No branches or pull requests

2 participants