You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Exceptionless 4.1.0 cannot navigate from the 'Parent' url #1287
My apologies for the delay I've been able to reproduce this. Looking into it, doesn't look like an event is being created with a reference id set for the parent scope. I'm not sure what should happen here. Seems like we aren't setting the reference id on any of our events that I can tell. We probably need to make a pass at this on the backend and through all of our logging clients.
I can locate that event using the filter ref.parent:fe7ce97e-e2ad-4531-863e-8879b70759f6.
However, when I try the filter pattern I found in the following code (reference:fe7ce97e-e2ad-4531-863e-8879b70759f6), I get an empty result:
I'm not very familiar with Exceptionless internals, so I'm not sure if the above information is enough to help identify the issue.
During my upcoming vacation, I might take some time to dig deeper into how Exceptionless handles ref.
Thanks for the report. We are closing this as part of an issue cleanup.
This was reported against Exceptionless 4.1.0 and the legacy UI. I checked the latest Svelte UI and did not find the same current "Parent" navigation surface, while the current event overview uses explicit faceted filter actions for related metadata.
If this is still reproducible in the latest app, please open a new issue with the current route, event payload, and the exact link/action that fails.
Activity
niemyjski commentedon Oct 22, 2019
How are you setting the reference id on the two submitted events?
BrisWhite commentedon Oct 23, 2019
Ok,Firstly,let me introduce my client project for you,it's based on dotnet core 2.2 framework,and here are my all procedures:
Exceptionless.Extensions.LoggingloggerFactory.AddExceptionless(key, url);That's all.Thanks for your reply!
niemyjski commentedon Oct 23, 2019
So the reference is coming from the begin scope? And you're expecting the three to be a child under the my state?
BrisWhite commentedon Oct 24, 2019
@niemyjski Exactly!
niemyjski commentedon Nov 12, 2019
Sorry for the delay I was on a long holiday. I'll have to take a look at this but I don't think we are adding a reference id on scopes
niemyjski commentedon Nov 12, 2019
Looks like we do create an event reference here: https://github.com/exceptionless/Exceptionless.Net/blob/master/src/Platforms/Exceptionless.Extensions.Logging/ExceptionlessLogger.cs#L91-L92 I'll try and add some tests to see what's going on.
BrisWhite commentedon Nov 14, 2019
@niemyjski Ok!many thanks!(* ̄︶ ̄)
niemyjski commentedon Apr 3, 2020
My apologies for the delay I've been able to reproduce this. Looking into it, doesn't look like an event is being created with a reference id set for the parent scope. I'm not sure what should happen here. Seems like we aren't setting the reference id on any of our events that I can tell. We probably need to make a pass at this on the backend and through all of our logging clients.
yangon99 commentedon Sep 25, 2025
Hello, I'm encountering the exact same issue with Exceptionless 8.1.6.
Is there a known solution or workaround?
niemyjski commentedon Sep 27, 2025
@yangon99 would you mind submitting a test or pr for this, would be a huge help
yangon99 commentedon Sep 28, 2025
@niemyjski
I have an event JSON from my self-hosted Exceptionless:
https://pastebin.com/cUWvcj1C
I can locate that event using the filter
ref.parent:fe7ce97e-e2ad-4531-863e-8879b70759f6.However, when I try the filter pattern I found in the following code (
reference:fe7ce97e-e2ad-4531-863e-8879b70759f6), I get an empty result:Exceptionless/src/Exceptionless.Web/Controllers/EventController.cs
Line 556 in 59fe164
I'm not very familiar with Exceptionless internals, so I'm not sure if the above information is enough to help identify the issue.
During my upcoming vacation, I might take some time to dig deeper into how Exceptionless handles ref.
Adds event reference test coverage
ejsmith commentedon Jun 22, 2026
Thanks for the report. We are closing this as part of an issue cleanup.
This was reported against Exceptionless 4.1.0 and the legacy UI. I checked the latest Svelte UI and did not find the same current "Parent" navigation surface, while the current event overview uses explicit faceted filter actions for related metadata.
If this is still reproducible in the latest app, please open a new issue with the current route, event payload, and the exact link/action that fails.