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

Multiple errors sent, only one received #238

Closed
paul-uz opened this issue Jun 1, 2024 · 10 comments
Closed

Multiple errors sent, only one received #238

paul-uz opened this issue Jun 1, 2024 · 10 comments
Labels

Comments

@paul-uz
Copy link

paul-uz commented Jun 1, 2024

I am sending multiple errors in a test function on AWS Lambda and I am using the new await version of send() with batches disabled in the client.

I only see one error in raygun after running the function.

@miquelbeltran
Copy link
Contributor

miquelbeltran commented Jun 2, 2024

Hi @paul-uz are the error instances grouped in Raygun?

For example, is the instance count correct, but all grouped in the same error?

image

@paul-uz
Copy link
Author

paul-uz commented Jun 2, 2024

Hi @paul-uz are the error instances grouped in Raygun?

No they weren't. I've tried to change to message based grouping and I think that helped a bit.

How up to date is the node hasher? It's on version 1 and the node package only just got an update in 2 years so maybe it needs some attention?

@miquelbeltran
Copy link
Contributor

Is there a change you can set the environment variable DEBUG to raygun and send us a log? The log should contain the lines [raygun.ts] Successfully sent message ... each time an error is sent using the send() method.

I need to check why the Raygun API is grouping errors even when the error.message is different.

@miquelbeltran
Copy link
Contributor

Can you also provide some sample code showing how you use the raygun client?

@paul-uz
Copy link
Author

paul-uz commented Jun 4, 2024

Right, changed back to message based grouping, and triggered two different errors, and it seems to be working now?

Provider based grouping still seems broken.

@miquelbeltran
Copy link
Contributor

Thanks for checking! I asked the team to review the hasher algorithm for the node provider. I will leave this ticket open until there are more updates.

@sumitramanga
Copy link
Collaborator

Hi team, sorry for the delay on this! I'm going to pass this onto this week's customer support engineer to take a look at this. Thanks so much for the additional context! We'll keep you well informed

@sumitramanga
Copy link
Collaborator

Hi Team,

We have an engineer looking into this issue. We'll let you know what we find based on our investigations.

Thank you for your patience!

@sumitramanga
Copy link
Collaborator

Hi team, this is still a work in progress at the moment. Replicating the issue is a bit of a tough one on our end but we'll continue to work away on this. Appreciate the patience!

@paul-uz Can you please send through information on your project set up like the Node version you are using. This would be very helpful !

@Pallesen01
Copy link

Hi @paul-uz, I've been unable to recreate this issue, would you be able to share anymore details about your test setup?

You could also try using our raygun4node-aws-lambda provider and see if that resolves the issue.

@Pallesen01 Pallesen01 closed this as not planned Won't fix, can't repro, duplicate, stale Aug 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Merged
Development

No branches or pull requests

4 participants