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

Source Amplitude: connector throws 404 when dont have any data #6375

Closed
harshithmullapudi opened this issue Sep 22, 2021 · 8 comments · Fixed by #6541
Closed

Source Amplitude: connector throws 404 when dont have any data #6375

harshithmullapudi opened this issue Sep 22, 2021 · 8 comments · Fixed by #6541
Assignees

Comments

@harshithmullapudi
Copy link
Contributor

Enviroment

OS Version / Instance: EC2 micro.a4
Memory / Disk: 12Gb / 256Tb SSD
Deployment: Kubernetes Airbyte
Version: 0.28.1-alpha
Source name/version: Amplitude 0.1.0
Destination name/version: Postgres

Current Behavior

I'm trying to sync for the first time and the process has been failed due to 404 errors from client api .

Expected Behavior

Tell us what should happen.

Logs

If applicable, please upload the logs from the failing operation.
For sync jobs, you can download the full logs from the UI by going to the sync attempt page and
clicking the download logs button at the top right of the logs display window.

LOG

replace this with
your long log
output here

Steps to Reproduce

Are you willing to submit a PR?

Remove this with your answer.

@harshithmullapudi harshithmullapudi added the type/bug Something isn't working label Sep 22, 2021
@blotouta2
Copy link
Contributor

File "/airbyte/integration_code/source_amplitude/api.py", line 160, in read_records
yield from super().read_records(sync_mode, cursor_field, stream_slice, stream_state)
File "/usr/local/lib/python3.7/site-packages/airbyte_cdk/sources/streams/http/http.py", line 228, in read_records
response = self._send_request(request)
File "/usr/local/lib/python3.7/site-packages/backoff/_sync.py", line 94, in retry
ret = target(*args, **kwargs)
File "/usr/local/lib/python3.7/site-packages/backoff/_sync.py", line 94, in retry
ret = target(*args, **kwargs)
File "/usr/local/lib/python3.7/site-packages/airbyte_cdk/sources/streams/http/http.py", line 204, in _send_request
response.raise_for_status()
File "/usr/local/lib/python3.7/site-packages/requests/models.py", line 943, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://amplitude.com/api/2/export?start=20210904T01&end=20210907T00

@marcosmarxm
Copy link
Member

Hi @blotouta2 from Amplitude docs, can you double check the start/end date you'd used?

404 Request data for a time range during which no data has been collected for the project, then you will receive a 404 response from our server.

@marcosmarxm marcosmarxm changed the title Connector Amplitude Bug Source Amplitude: connector throws 404 when dont have any data Sep 23, 2021
@blotouta2
Copy link
Contributor

Yes, i used start and end date from the current month.

@sherifnada sherifnada added the area/connectors Connector related issues label Sep 24, 2021
@sherifnada
Copy link
Contributor

@blotouta2 and you can confirm there is data in the account?

@blotouta2
Copy link
Contributor

Screenshot 2021-09-24 at 12 03 49 PM

@sherifnada dashboard shows that we have 256 events since last 1 month

@sherifnada
Copy link
Contributor

I think the correct way to handle a 404 then is to log it and not fail the connector

@gaart
Copy link
Contributor

gaart commented Oct 12, 2021

@harshithmullapudi

We just merged this feature into master and released a new version of the connector.

Upgrade your connector to version 0.1.3 and get started. To upgrade your connector version, go to the admin panel in the left hand side of the UI, find this connector in the list, and input the latest connector version.

Please let us know if you have any further questions.

Enjoy!

@marcosmarxm
Copy link
Member

@blotouta2 can you check the new version of this connector and test it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants