v1.1 2012-03-07

Owned by ise (Unlicensed)
Last updated: Mar 09, 2012
3 min read

Still to be defined

  1. Name for the Environment does not match, I propose something like Configuration
  2. Where will user for example define exclude rules, is this part of the Profile Manager?
  3. Sensor definitions are hidden away from user, but what does this mean? No possibility to change the default sensors? All sensors apply for all Environment?
  4. All the things written directly on the sketches

Conclusions after /wiki/spaces/ARCHIVE/pages/5019327

  • In agent mapping environment can be selected with drop down box
  • If for an agent there are two possible environment in the mapping, do not connect agent, provide log info
  • In general it would be good to have a log information in GUI, so that information like Agent registered, Not-registered, etc could be seen by the user
  • Do not include lables support for first phase
  • Changing the server in one manager, changes it all manager
  • Provide properties sub-view for managers (similar like for storage now)
  • Include description where possible, as much as possible (profile, agent mapping, environment,..)
  • Save button should be in the toolbar (maybe also some standard options also)
  • In the change history we can visualize more the actions, and we can in the future provide the information what did change between versions (like what Method def where added, what removed)
  • In the future maybe option compare profile versions
  • For the profile, do not have the exclude rules separately, but add possibility to add exclude rules in Method Def and Exception Def
  • Provide a column (first) only with images that visualize the method def: sensor type, class/interface/super-class, modifiers, annotation
  • Other options are visualized in the options column
  • Special radio buttons for interface/super-class
  • Button for pop=up window where all classes already loaded on the server could be searched, like class explorer in Eclipse. Same for annotations
  • For parameters, if they are directly specified, allow user to select which one to capture. Otherwise he can add parameters with position/name.
  • + - sign next to fields
  • In future test button will be nice, to see what classes will be instrumented with current profile against already loaded classes on the server
  • Interface and annotation also for exceptions
  • Simple/enhance option not in right place, move to General settings
  • String length per sensor type also to the General settings
  • Only one global exclude
  • This how the user can add/remove/edit global excludes

Sketches