Use this view to examine the values of any attributes (properties) for which data is collected.
In the JMX Explorer Available MBeans view, select an MBean. If attributes are being monitored, the view is populated.
Attribute Value. For more information, see MBean Property summary view. |
Use this view to review the latest value, period values, description, and source of the attribute.
In the JMX Explorer Available MBeans view, select an MBean. In the MBean Properties view, click the value of an attribute.
Edit Configuration. Opens the Attribute — Topology Property Configuration dialog box, which allows you to edit the name, storage type, and metric derivations (if applicable). |
Use the JVM dashboard to review the operating status of a selected JVM.
On the JMX Explorer dashboard, click the JVM name. The JVM Summary view pop-up opens. Click the Heap Usage chart to open the JVM dashboard.
Click any of the tabs to view details about the selected JVM metric. |
Regular expressions employ metacharacters. A metacharacter is a character with special meaning. It does not denote a normal letter, but instead affects the interpretation of other characters in a regular expression. Metacharacters only occur inside a regular expression; for example, an asterisk (*) in a data string is not a metacharacter. There are only a few metacharacters in the regular expression language, but their effect can be powerful.
For example: the regular expression ‘White *space’ matches ‘Whitespace’, or ‘White space’, or ‘White@@any number of space characters@@space’, but not ‘White *space’ (the string containing a literal asterisk). NOTE: ‘nexus*’ does NOT match ‘nexus.bat’, or ‘nexusconfig’. Path name-style matching (file globbing) is not the same as regular expression syntax. | |||||
The combination ‘.*’ (dot-star) matches any string of characters. It is an idiom for ‘the rest of the characters’ in a string, but not including the end of line character. For example: the regular expression ‘HTTP.*’ matches ‘HTTP1.0’, or CAUTION: The regular expression ‘mayb.com.*’ matches ‘maybecompletely wrong!’. The dot in the regular expression matches any character, in this case an ‘e’.
NOTE: Because the dot is a metacharacter, use the character class [.] to match a literal dot in a string. It is more robust than attempting to protect the dot with a backslash (\.). | |||||
For example: the regular expression ‘i?www’ matches ‘www’ or ‘iwww’. The regular expression ‘(ab)?cd’ matches ‘abcd’ and ‘cd’. | |||||
For example: the regular expression ‘i+www’ matches ‘iwww’ or ‘iiwww’, but not ‘www’. | |||||
For example: the regular expression ‘[bcp]at’ matches ‘bat’, ‘cat’, or ‘pat’, but not ‘mat’. | |||||
For example: the regular expression ‘[b-h]at’ matches ‘bat’, or ‘cat’, or ‘fat’, or ‘hat’, but not ‘mat’. | |||||
Unless it appears as the first entry in a bracketed character class, the caret metacharacter matches the special character that represents the start of a string. The combination ‘[^...]’ represents a negated character class. All characters except the ones listed are allowed in the match.
| |||||
NOTE: The dollar sign ($) is a shell metacharacter in Unix. If you are running Cartridge for JMX on a UNIX® system and want to include the dollar sign as a metacharacter in a regular expression, surround the expression with single quotes. For example: sh nexusctl.sh start-recording -fir ‘\.[Gg][Ii][Ff]($|\?)/’ | |||||
The vertical bar metacharacter matches either of the expressions it separates. For example: the regular expression ‘foo|bar’ matches ‘foo’ or ‘bar’, but not ‘foobar’. | |||||
For example: the regular expression ‘myhost\.com’ matches ‘myhost.com’, but not ‘myhostcom’. | |||||
Parentheses are used for group, for example, to limit the scope of the ‘or’ operator. For example: the regular expression ‘http://(my|our)host\.com’ matches ‘http://myhost.com’ or ‘http://ourhost.com’. |
© ALL RIGHTS RESERVED. Termini di utilizzo Privacy Cookie Preference Center