Skip to content

Exceptionless 4.1.0 cannot navigate from the 'Parent' url #1287

Closed as not planned

Description

@BrisWhite

Just like title said,when i click the 'Parent' url,I got nothing.

1
2

But I can use a query filter like this to achieve my goal:
(idx.parent-r:63cb4802-3e26-48ee-b4b6-3b1a386e83e3)

Activity

  1. niemyjski commented on Oct 22, 2019

    @niemyjski
    Member

    How are you setting the reference id on the two submitted events?

  2. BrisWhite commented on Oct 23, 2019

    @BrisWhite
    Author

    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:

    1. Import nuget package,Exceptionless.Extensions.Logging
    2. In "Configure" method,I invoke this method,loggerFactory.AddExceptionless(key, url);
    3. In whatever Contoller,I use logger like this way:
    using (var scope = logger.BeginScope(“my state”))
    {
        logger.LogInformation("test 1");
        logger.LogInformation("test 2");
        logger.LogInformation("test 3");
    }

    That's all.Thanks for your reply!

  3. niemyjski commented on Oct 23, 2019

    @niemyjski
    Member

    So the reference is coming from the begin scope? And you're expecting the three to be a child under the my state?

  4. BrisWhite commented on Oct 24, 2019

    @BrisWhite
    Author

    @niemyjski Exactly!

  5. niemyjski commented on Nov 12, 2019

    @niemyjski
    Member

    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

  6. niemyjski commented on Nov 12, 2019

    @niemyjski
    Member

    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.

  7. BrisWhite commented on Nov 14, 2019

    @BrisWhite
    Author

    @niemyjski Ok!many thanks!(* ̄︶ ̄)

  8. self-assigned this
    on Apr 3, 2020
  9. niemyjski commented on Apr 3, 2020

    @niemyjski
    Member

    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.

  10. yangon99 commented on Sep 25, 2025

    @yangon99

    Hello, I'm encountering the exact same issue with Exceptionless 8.1.6.
    Is there a known solution or workaround?

  11. niemyjski commented on Sep 27, 2025

    @niemyjski
    Member

    @yangon99 would you mind submitting a test or pr for this, would be a huge help

  12. yangon99 commented on Sep 28, 2025

    @yangon99

    @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:

    return await GetInternalAsync(sf, ti, String.Concat("reference:", referenceId), null, mode, page, limit, before, after);

    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.

  13. added a commit that references this issue on Jan 20, 2026
  14. ejsmith commented on Jun 22, 2026

    @ejsmith
    Member

    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.

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

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions