org.apache.jmeter.visualizers
Class MonitorHealthVisualizer
- ChangeListener, Clearable, GraphListener, ImageVisualizer, ItemListener, JMeterGUIComponent, Printable, UnsharedComponent, Visualizer
public class MonitorHealthVisualizer
For performance reasons, I am using tabs for the visualizers. Since a
visualizer is heavy weight, I don not want to have two separate result
collectors rather the same information. Instead, I would rather have the
visualizer be the container for the data and simply pass the data to child
JComponents. In the future, we may want to add email alerts as a third tab.
void | add(SampleResult res) - Because of the unique requirements of a monitor We have to handle the
results differently than normal GUI components.
|
void | clearData() - Clears the MonitorAccumModel.
|
void | configure(TestElement el) - The GUI must be able to extract the data from the TestElement and update
all GUI fields to represent those data.
|
Image | getImage()
|
String | getLabelResource() - Get the component's resource name, which getStaticLabel uses to derive
the component's label in the local language.
|
void | itemStateChanged(ItemEvent e)
|
void | modifyTestElement(TestElement c) - GUI components are responsible for populating TestElements they create
with the data currently held in the GUI components.
|
void | updateGui()
|
void | updateGui(Sample s)
|
clearGui , configure , configureTestElement , createTestElement , getErrorLoggingCheckbox , getFile , getFilePanel , getModel , isStats , makeTitlePanel , modifyTestElement , setFile , setModel , stateChanged |
clearGui , configure , configureTestElement , createTitleLabel , getComment , getDocAnchor , getName , getNamePanel , getNode , getPrintableComponent , getStaticLabel , isEnabled , makeBorder , makeScrollPane , makeScrollPane , makeTitlePanel , setComment , setEnabled , setName , setNode |
MonitorHealthVisualizer
public MonitorHealthVisualizer()
Constructor for the GraphVisualizer object.
add
public void add(SampleResult res)
Because of the unique requirements of a monitor We have to handle the
results differently than normal GUI components. A monitor should be able
to run for a very long time without eating up all the memory.
- add in interface Visualizer
clearData
public void clearData()
Clears the MonitorAccumModel.
- clearData in interface Clearable
configure
public void configure(TestElement el)
The GUI must be able to extract the data from the TestElement and update
all GUI fields to represent those data. This method is called to allow
JMeter to show the user the GUI that represents the test element's data.
- configure in interface JMeterGUIComponent
- configure in interface AbstractVisualizer
getLabelResource
public String getLabelResource()
Get the component's resource name, which getStaticLabel uses to derive
the component's label in the local language. The resource name is fixed,
and does not vary with the selected language.
Normally this method should be overriden in preference to overriding
getStaticLabel(). However where the resource name is not available or required,
getStaticLabel() may be overridden instead.
- getLabelResource in interface JMeterGUIComponent
itemStateChanged
public void itemStateChanged(ItemEvent e)
modifyTestElement
public void modifyTestElement(TestElement c)
GUI components are responsible for populating TestElements they create
with the data currently held in the GUI components. This method should
overwrite whatever data is currently in the TestElement as it is called
after a user has filled out the form elements in the gui with new
information.
- modifyTestElement in interface JMeterGUIComponent
- modifyTestElement in interface AbstractVisualizer
Copyright © 1998-2010 Apache Software Foundation. All Rights Reserved.