Skip to content

[Errors Inbox]: It's not clear how to remove entity_id from fingerprint evaluation logic #20287

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

Open
k-rudy opened this issue Mar 24, 2025 · 1 comment
Labels
content requests related to docs site content

Comments

@k-rudy
Copy link

k-rudy commented Mar 24, 2025

Hi guys,

We're having a problem that is well described in the documentation:

If you have a single application reporting as multiple entities in New Relic (running in different clusters, cells, etc.), you might see duplicate error groups, since our grouping logic looks at account and entity IDs as part of the fingerprinting process.

So we need to remove Entity ID out of the fingerprinting process, while keeping all remaining logic as it is.

The Ruby agent documentation for the fingerprinting in the Agent describes the process as this:

proc = proc { |hash| "Access" if hash[:'http.statusCode'] == 401 }
NewRelic::Agent.set_error_group_callback(proc)

But it's not clear how default fingerprinting can be achieved using the error group callback. If we knew that - it would be very easy to adjust the logic to remove entity ID from it, otherwise the documentation is not very usable.
Can you please provided that? Can be pseudocode or anything. As it's not clear how to extract all default fingerprint attributes out of hash Proc param.

Any help will be very much appreciated
Konstantin.

@k-rudy k-rudy added the content requests related to docs site content label Mar 24, 2025
Copy link

Hi @k-rudy 👋

Thank you for filing an issue! We'll triage your issue and let you know if we have questions, and then route it to the appropriate team so we can get it solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content requests related to docs site content
Projects
None yet
Development

No branches or pull requests

1 participant