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

Sentry stopped processing queries #3333

Closed
barisyild opened this issue Sep 19, 2024 · 9 comments
Closed

Sentry stopped processing queries #3333

barisyild opened this issue Sep 19, 2024 · 9 comments

Comments

@barisyild
Copy link

Self-Hosted Version

24.9.0

CPU Architecture

x86_64

Docker Version

27.2.1

Docker Compose Version

2.29.2

Steps to Reproduce

idk

Expected Result

Sentry should have continued processing queries.

Actual Result

Issue reporting, Profiles working but queries not working.

Event ID

No response

@hubertdeng123
Copy link
Member

You will need to give more information if you'd like our support.

@barisyild
Copy link
Author

You will need to give more information if you'd like our support.

After restarting the server several times it stopped processing queries.

I don't know exactly what kind of log I should send.

@aldy505
Copy link
Collaborator

aldy505 commented Oct 6, 2024

Try to provide us the instrumentation code you're sending to your self-hosted instance. After the program sent the event (check this by enabling the debug option on your SDK), try to observe the relay container, see if it's rejecting the event. If no logs are shown, try to check post-process-forwarder-transactions, subscription-consumer-transactions, and snuba-spans-consumer containers. Is there any error logs there?

@barisyild
Copy link
Author

DEBUG: Capturing transaction: 1f13e6456e2142f783e94fe39cd6e4c1
DEBUG: Attaching client report to envelope.
DEBUG: Serializing object: [censored]
DEBUG: Serializing object: [censored]
ERROR: Request failed, API returned 403
ERROR: {"detail":"event submission rejected with_reason: ProjectId"}
ERROR: The transport failed to send the envelope with response code 403
ERROR: Envelope submission failed
 java.lang.IllegalStateException: The transport failed to send the envelope with response code 403
java.lang.IllegalStateException: The transport failed to send the envelope with response code 403
        at io.sentry.transport.AsyncHttpTransport$EnvelopeSender.flush(AsyncHttpTransport.java:320)
        at io.sentry.transport.AsyncHttpTransport$EnvelopeSender.run(AsyncHttpTransport.java:243)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:829)

@hubertdeng123
Copy link
Member

Can you make sure that your DSN matches what the project should be?

@barisyild
Copy link
Author

Can you make sure that your DSN matches what the project should be?

Yeah matches because reports issues.

@barisyild
Copy link
Author

Nuclear Option fixed my issue.

@wilkis3
Copy link

wilkis3 commented Oct 22, 2024

Nuclear Option fixed my issue.

Quickie: The nuclear option deletes only the queries, events etc. and not the settings and DSNs?

@barisyild
Copy link
Author

Nuclear Option fixed my issue.

Quickie: The nuclear option deletes only the queries, events etc. and not the settings and DSNs?

The queue must have been broken for some reason.

I had problems with kafka offset.

@github-actions github-actions bot locked and limited conversation to collaborators Nov 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
Archived in project
Archived in project
Development

No branches or pull requests

4 participants