search

chatwoot / chatwoot

Open-source live-chat, email support, omni-channel desk. An alternative to Intercom, Zendesk, Salesforce Service Cloud etc. 🔥💬
https://www.chatwoot.com/help-center
Other
21.37k stars 3.62k forks source link

After upgrade to >= 3.1 version, high bandwidth call to US #8595

Closed thanhpd56 closed 9 months ago

thanhpd56 commented 11 months ago

Describe the bug

After we upgrade to version >= 3.1, our monthly Google cloud billing increase significantly. We investigate by Grafana and see that the outgoing traffic increased significantly after upgrade. I already disable telemetry, but nothing changes.

To Reproduce

Upgrade to version 3.1, and see the traffic analytic.

Expected behavior

No response

Environment

Kubernetes

Cloud Provider

GCP

Platform

None

Operating system

No response

Browser and version

No response

Docker (if applicable)

3.1

Additional context

No response

linear[bot] commented 11 months ago

PR-805 After upgrade to >= 3.1 version, high bandwidth call to US

sojan-official commented 11 months ago

@thanhpd56 We haven't added anything additional in telemetry. Please share additional information on network calls being made.

thanhpd56 commented 11 months ago

@thanhpd56 We haven't added anything additional in telemetry. Please share additional information on network calls being made.

Hi, thanks for your response. Below are the grafana network metric: Before upgrade: image After upgrade: image From gcloud billing:

image
sojan-official commented 11 months ago

@thanhpd56 I can't spot anything specific from the provided information. Which channels do you use primarily in your Chatwoot installation ? the only calls Chatwoot should be making to external services would the required API calls for external channels like whatsapp and also for integrations like openai

thanhpd56 commented 11 months ago

@sojan-official we have website channel, facebook channel, and Zalo (api channel). Additionally, these channels do not have many messages each day.

thanhpd56 commented 11 months ago

The first time we faced to this issue, then I had to downgrade to version 3.0. Recently I upgraded to version 3.2 but the issue still happend, so I have to downgrade again. :(

pranavrajs commented 9 months ago

Closing this here as we don't have enough information to debug this further. Please feel free to re-open this with information to debug.

github-actions[bot] commented 8 months ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.