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

[APM] Set up routing for Services and Traces views #23824

Closed
formgeist opened this issue Oct 4, 2018 · 5 comments
Closed

[APM] Set up routing for Services and Traces views #23824

formgeist opened this issue Oct 4, 2018 · 5 comments
Assignees
Labels
Team:APM All issues that need APM UI Team support v6.6.0

Comments

@formgeist
Copy link
Contributor

formgeist commented Oct 4, 2018

Since we're adding a new Traces view, we want to be able to route directly to the Traces view i.e. from InfraOps UI. Currently there's no routing in place to handle going to either Services or Traces.

Services: /app/apm/services
Traces: /app/apm/traces

@formgeist formgeist added Team:APM All issues that need APM UI Team support [zube]: Inbox v6.5.0 labels Oct 4, 2018
@elasticmachine
Copy link
Contributor

Pinging @elastic/apm-ui

@sorenlouv
Copy link
Member

@jasonrhodes Is this something you can take a stab at?

@jasonrhodes
Copy link
Member

Sure! @formgeist for these pages, do we want to just duplicate the existing homepage but without the tabs for now? (i.e. services is just the content from the homepage services tab, traces just the content from the homepage traces tab)

@jasonrhodes
Copy link
Member

@formgeist and I discussed in Zoom:

  • The new routes will point to the existing APM homepage but with the "services" or "traces" tab active
  • Clicking on the tabs will update the route
  • The APM homepage will redirect to /services for now

@sorenlouv
Copy link
Member

Deferred to 6.6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:APM All issues that need APM UI Team support v6.6.0
Projects
None yet
Development

No branches or pull requests

5 participants