Unknown macro: {float}
Summary of old meetings
During the conceptional phase of the configuration interface meetings were hold. A new version of the configuration interface was designed after each meeting. Many points of the outcoming of the meetings were integrated into the new version. The summary shows the outstanding points and the ideas for future versions.
The summary contains the following meetings:
- 2009-10-09 Configuration Interface
- /wiki/spaces/ARCHIVE/pages/5019353
- /wiki/spaces/ARCHIVE/pages/5019343
- /wiki/spaces/ARCHIVE/pages/5019358
Outstanding points
2009-10-09
- Name "environment" might be mis-leading => Discuss
- Profile
- Active profile should easily seen on the user interface => color, icon, both ??
2009-10-16
- Read-only profiles => presentation necessary ??
- Out-of-the-box profiles can be read-only
- Currently only JDBC
- JDBC Sensors should not be usable by the UI!
2009-10-30
- Create icons to mark that a sensor is using superclass or interface to be able to easily see this => Decoration would be nice
- Think of a better name for "sensor configuration perspective"
Additional information
- Profile
- IP/port/agent name must directly be provided by the agent (best way to do that is by using -D parameters)
- Grouping possibilities
- Apart from "show per sensortype" and "show as package structure"
- "Only wildcards"
- interfaces, superclass, ...
- "not instrumented sensor definitions" -> possibly to remove unnecessary sensor types
- "include sensors defined by included profiles"
Ideas for future versions
- include annotations to the instrumentation window (not yet, but in a later release)
- Auto completion of the definition of packages/classes/methods (later!)
- Graphical representation of the tree structure of the included profiles. which agent uses which and so on
- Create a report for the sensor definitions
Open questions, extensions and todos
- We missing out on the exception sensor (todos added in respective wiki pages)