-
Notifications
You must be signed in to change notification settings - Fork 125
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
Personalization of causation/correlation/type streams for browser #626
Comments
Is this still an issue? |
The behavior mentioned above is still the case, and still confusing. If you don't set up the What I don't understand: why doesn't the ShowEvent view just show links to all streams that contain the event? That would be much more useful to me. |
Good question! There's already an API for that — |
This leads to some duplication with how type/correlation/causation streams are currently displayed. I'll deal with them next. #626 (comment)
Scheduled for next release. |
Currently, displaying links (at browser) to correlation / causation / type streams work with assumption that our
LinkBy*
handlers are used with default prefix ($by_correlation_
,$by_causation_
,$by_type_
) and with default metadata field (correlation_id
,causation_id
, event type).There are two parts of this task:
$by_correlation_
,$by_causation_
,$by_type_
mentioned above)correlation_id
,causation_id
)IMO the first task is more important than the second.
The text was updated successfully, but these errors were encountered: