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

Camel - Trace & debug #23

Closed
Tracked by #12
tadayosi opened this issue Jan 18, 2023 · 0 comments
Closed
Tracked by #12

Camel - Trace & debug #23

tadayosi opened this issue Jan 18, 2023 · 0 comments
Assignees
Labels
area/camel kind/feature New feature or request
Milestone

Comments

@tadayosi
Copy link
Member

Camel plugin should provide the features of tracing and debugging Camel routes from the web console. Tracing and debugging are backed by the following Camel features:

Trace

Trace

Debug

Debug

@tadayosi tadayosi mentioned this issue Jan 18, 2023
18 tasks
@tadayosi tadayosi added the kind/feature New feature or request label Jan 26, 2023
@tadayosi tadayosi added this to the 0.3.0 milestone Jan 30, 2023
@phantomjinx phantomjinx self-assigned this Mar 21, 2023
phantomjinx added a commit to phantomjinx/hawtio-next that referenced this issue May 3, 2023
* CamelContext.tsx
 * Replaces the camel context with the route diagram context
 * Changes the component property is NavItem to component function thereby
   allowing flexibility in adding additional component structure, like
   ContextProviders
 * Allocates the RouteDiagramContext to the RouteDiagram component
 * Adds the Debug component to the set of views

* Debug.tsx
 * Debug view component
 * Implements all functionality of original debug view but adds the bottom
   panel to a sliding-in drawer panel

* RouteDiagram.tsx
 * Adds option of displaying annotations from the context
 * Adds option of adding a double-click action from the context
 * Makes showing the statistics popover optional (not required in debug)
 * Turned on fitView to ensure all nodes are displayed

* RouteDiagram.css
 * To make room for annotations, the diagram node layout is converted to
   grid layout

* visualization-service.ts
 * Adds a routeId to the node properties to index the node within the
   route while the id is across all routes
phantomjinx added a commit to phantomjinx/hawtio-next that referenced this issue May 3, 2023
* CamelContext.tsx
 * Replaces the camel context with the route diagram context
 * Changes the component property is NavItem to component function thereby
   allowing flexibility in adding additional component structure, like
   ContextProviders
 * Allocates the RouteDiagramContext to the RouteDiagram component
 * Adds the Debug component to the set of views

* Debug.tsx
 * Debug view component
 * Implements all functionality of original debug view but adds the bottom
   panel to a sliding-in drawer panel

* RouteDiagram.tsx
 * Adds option of displaying annotations from the context
 * Adds option of adding a double-click action from the context
 * Makes showing the statistics popover optional (not required in debug)
 * Turned on fitView to ensure all nodes are displayed

* RouteDiagram.css
 * To make room for annotations, the diagram node layout is converted to
   grid layout

* visualization-service.ts
 * Adds a routeId to the node properties to index the node within the
   route while the id is across all routes
phantomjinx added a commit to phantomjinx/hawtio-next that referenced this issue May 3, 2023
* CamelContext.tsx
 * Replaces the camel context with the route diagram context
 * Changes the component property is NavItem to component function thereby
   allowing flexibility in adding additional component structure, like
   ContextProviders
 * Allocates the RouteDiagramContext to the RouteDiagram component
 * Adds the Debug component to the set of views

* Debug.tsx
 * Debug view component
 * Implements all functionality of original debug view but adds the bottom
   panel to a sliding-in drawer panel

* RouteDiagram.tsx
 * Adds option of displaying annotations from the context
 * Adds option of adding a double-click action from the context
 * Makes showing the statistics popover optional (not required in debug)
 * Turned on fitView to ensure all nodes are displayed

* RouteDiagram.css
 * To make room for annotations, the diagram node layout is converted to
   grid layout

* visualization-service.ts
 * Adds a routeId to the node properties to index the node within the
   route while the id is across all routes
phantomjinx added a commit to phantomjinx/hawtio-next that referenced this issue May 10, 2023
* Message detail panel is used in both debug and trace views so breaks it
  out into its own component

* MessageDrawer supports an extra panel to cover the breakpoint list in
  the debug view
phantomjinx added a commit to phantomjinx/hawtio-next that referenced this issue May 10, 2023
* Builds on similar functionality and abilities of Debug view
phantomjinx added a commit to phantomjinx/hawtio-next that referenced this issue May 10, 2023
* Turns out one can add additional tags (context provider) around the
  main component tag and still qualify as a JSX.Element
phantomjinx added a commit to phantomjinx/hawtio-next that referenced this issue May 10, 2023
* Simplifies Debug.tsx by moving the conditional breakpoint modal component
  into its own file
phantomjinx added a commit to phantomjinx/hawtio-next that referenced this issue May 10, 2023
* Reduces the number of re-renderings based on breakpoints by checking the
  previous breakpoints using a ref

* Removes usage of '... as type' and check for nulls|undefined instead

* Reduces useEffect functions for simplifying state
phantomjinx added a commit to phantomjinx/hawtio-next that referenced this issue May 10, 2023
phantomjinx added a commit to phantomjinx/hawtio-next that referenced this issue May 10, 2023
tadayosi pushed a commit that referenced this issue May 15, 2023
* CamelContext.tsx
 * Replaces the camel context with the route diagram context
 * Changes the component property is NavItem to component function thereby
   allowing flexibility in adding additional component structure, like
   ContextProviders
 * Allocates the RouteDiagramContext to the RouteDiagram component
 * Adds the Debug component to the set of views

* Debug.tsx
 * Debug view component
 * Implements all functionality of original debug view but adds the bottom
   panel to a sliding-in drawer panel

* RouteDiagram.tsx
 * Adds option of displaying annotations from the context
 * Adds option of adding a double-click action from the context
 * Makes showing the statistics popover optional (not required in debug)
 * Turned on fitView to ensure all nodes are displayed

* RouteDiagram.css
 * To make room for annotations, the diagram node layout is converted to
   grid layout

* visualization-service.ts
 * Adds a routeId to the node properties to index the node within the
   route while the id is across all routes
tadayosi pushed a commit that referenced this issue May 15, 2023
* Message detail panel is used in both debug and trace views so breaks it
  out into its own component

* MessageDrawer supports an extra panel to cover the breakpoint list in
  the debug view
tadayosi pushed a commit that referenced this issue May 15, 2023
* Builds on similar functionality and abilities of Debug view
tadayosi pushed a commit that referenced this issue May 15, 2023
* Turns out one can add additional tags (context provider) around the
  main component tag and still qualify as a JSX.Element
tadayosi pushed a commit that referenced this issue May 15, 2023
* Simplifies Debug.tsx by moving the conditional breakpoint modal component
  into its own file
tadayosi pushed a commit that referenced this issue May 15, 2023
* Reduces the number of re-renderings based on breakpoints by checking the
  previous breakpoints using a ref

* Removes usage of '... as type' and check for nulls|undefined instead

* Reduces useEffect functions for simplifying state
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/camel kind/feature New feature or request
Projects
Archived in project
Development

No branches or pull requests

2 participants