Feedback on "Fault" interface

  • 0
  • 1
  • Idea
  • Updated 4 years ago
  • Planned
I have some feedback regarding the UI for faults. See attached picture:

 

A few problems with it:

  • The fault window is very small, and currently it is not possible to resize this window. 
  • As you clear faults, the pagination seems to break (for example, try clearing some faults, then navigating to the next page).
  • The date and db group / name are lumped together, making it impossible to tell what database is generating a fault without first expanding the fault.
  • Expanding a fault takes > 300 ms and feels clunky.
I would also suggest that faults such as "The database is down" should automatically be marked as resolved if I start up the VDB through Delphix's UI.

P.S., is there a plan to move Delphix's UI out of flash and into standard HTML?
Photo of Avindra Goolcharan

Avindra Goolcharan

  • 404 Points 250 badge 2x thumb

Posted 4 years ago

  • 0
  • 1
Photo of DJ Burrowes

DJ Burrowes

  • 624 Points 500 badge 2x thumb

Hello Avindra,

Thanks for your feedback! I'm one of the UI engineers here at Delphix, and making the faults display better is definitely on our list of things to improve.  (please keep your comments coming)

We are also in the process of doing some parts of our interface in HTML in the future.  I'm curious why you care about the implementation technology?  (that is, why do you want it to be moved out of Flash?)

dj burrowes
Photo of Avindra Goolcharan

Avindra Goolcharan

  • 404 Points 250 badge 2x thumb
Hi David, great to hear that the fault display is on the list. I asked about the implementation technology because I do some UI work myself, and am interested in the development process at Delphix.
Photo of DJ Burrowes

DJ Burrowes

  • 624 Points 500 badge 2x thumb
Good day Avindra,

That makes sense (being interested in the dev process).  Can I answer more questions you have?

dj
Photo of Avindra Goolcharan

Avindra Goolcharan

  • 404 Points 250 badge 2x thumb
Sure! I read some posts on the Delphix blog and saw pieces of the architecture when an engineer was debugging an issue. My understanding is that the backend is written using a combination of Java running on Tomcat and JavaScript (node.js). Do you have separate teams working on different components? Or do Delphix engineers touch on all pieces of the architecture?
Photo of DJ Burrowes

DJ Burrowes

  • 624 Points 500 badge 2x thumb
You touch on some of the cool things about our culture.
First, a bit on the technology: the core backend is written in Java, while the OS level stuff is in C/C++ of course.  The CLI is in node.js and the browser client is flex & javascript.
However, organizationally, we are not divided into separate groups (e.g. only some people can touch the Java, while only others can touch the C). We don't even have "teams" in that sense. Instead, we tend to organize around functional units (e.g. a team organizes around a project).  We want to make it possible for a single person to make a change in the OS, make the corresponding change in the app server side, and then reflect that change through the web services, cli and gui.  There's no silos here.