. . . . . . . . . . . . . . . 27 5.2.2 Cross referencing: the link tag . . . . . . . . . . . . . . . . . . . . . . . . 27 5.3 Tag reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 5.3.14 fpdoc-description : Global tag . . . . . . . . . . . . . . . . . . . . . . . . 33 5.3.15 i : Format italics . . . . . . . . . . FPDOC USAGE --charset=UTF8 will result in an UTF8 specification of the content attribute of the meta tag in the generated HTML file: 3

document heading 3.1. The title tag 3.2. The script tag 3.3. The noscript tag 3.4. The link tag 3.5. The style tag 3.6. The base tag 3.7. The meta tag 4. The document body 4.1. Block 5. Tags that interact with text 5.1. The p tag 5.2. The span tag 5.3. The br tag 5.4. The heading tags 5.5. The strong tag 5.6. The em tag 5.6.1. Quotes 5.7. Horizontal line 5.8. Code nav 7.2.2. aside 7.2.3. header 7.2.4. main 7.2.5. footer 8. Forms 8.1. The input tag 8.1.1. Email 8.1.2. Password 8.1.3. Numbers 8.1.4. Hidden field 8.1.5. Setting a default value

alarms.get[], vmware.dc.alarms.get[], vmware.hv.alarms.get[], vmware.vm.alarms.get[]. • Collecting tag information from different VMware components: vmware.cluster.tags.get[], vmware.datastore.tags.get[] simplify further processing of the returned JSON (for example, in preprocessing steps or LLD macros). Tag reading from VMware VMware items reporting various VMware tags (e.g., vmware.datastore.tags.get[]) attention such as a trigger changing state or a discovery/agent autoregistration taking place. event tag - a pre-defined marker for the event. It may be used in event correlation, permission granulation

Zabbix. Tag-based mapping of services to problems The availability of services in previous Zabbix versions depended on triggers and their states. In the new version that is replaced by a tag-based mapping unacknowledged problems will be included; • ProblemTagFilter - if specified, only triggers with the specified tag name will be included; • TrapTimer - if set, Zabbix will send no more than one trap of the highest subfilter shows clickable links allowing to filter items based on a common entity - the host, tag name or tag value. As soon as the entity is clicked, items are immediately filtered. For more details,

attention such as a trigger changing state or a discovery/agent autoregistration taking place. event tag - a pre-defined marker for the event. It may be used in event correlation, permission granulation order to increase logging level, modify file lib/logback.xml and change the level attribute of tag to ”debug”: Note that unlike Zabbix server record per event. That means additional 80 bytes per event. Optionally events can have tags, each tag record requiring approximately 100 bytes of disk space1. The number of tags per event (#tags) depends

stream item values and events from Zabbix to external systems over HTTP (see protocol details). The tag filter can be used to stream subsets of item values or events. Warning: This feature currently has been improved to convert to UTF-8 from the character set specified in the HTTP header or HTTP meta tag. Templates New templates New template is available: • HPE iLO by HTTP You can get this template: attention such as a trigger changing state or a discovery/agent autoregistration taking place. event tag - a pre-defined marker for the event. It may be used in event correlation, permission granulation

avg(last_foreach(/*/system.cpu.load?[group=”Servers A” and group=”Servers B” and group=”Servers C” and (tag=”Service:” or tag=”Importance:High”)])) Not available/supported Aggregation with complex filters {{?trendavg(//system by tag name only • based on tags not having the specified name or value This is implemented by adding new operators ”Exists”, ”Does not exist”, ”Does not equal” and ”Does not contain” in the tag filter attention such as a trigger changing state or a discovery/agent autoregistration taking place. 23 event tag - a pre-defined marker for the event. It may be used in event correlation, permission granulation

. . . . . . . . . . . . . . . . . . . . . . . 20 5.4. Markup inheritance with the wicket:extend tag. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 5.5. Summary 28 6.2. Modifing tag attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 6.3. Generating tag attribute 'id' . . . . . . . . . . . . . . . . . . 33 6.9. Hiding decorating elements with the wicket:enclosure tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 6.10. Surrounding existing markup

. . . . . . . . . . . . . . . . . . . . . . . 20 5.4. Markup inheritance with the wicket:extend tag. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 5.5. Summary 27 6.2. Modifing tag attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 6.3. Generating tag attribute 'id' . . . . . . . . . . . . . . . . . . 33 6.9. Hiding decorating elements with the wicket:enclosure tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 6.10. Surrounding existing markup

"content" %}. You’ll also see {% load cms_tags %} in that file - cms_tags is the required template tag library. If you’re not already familiar with Django template tags, you can find out more in the Django 2.4. Rendering Menus In order to render the CMS’s menu in your template you can use the show_menu tag. Any template that uses show_menu must load the CMS’s menu_tags library first: {% load menu_tags %} This is worth explaining in a little detail: {% load cms_tags sekizai_tags %} loads the template tag libraries we use in the template. {% page_attribute "page_title" %} extracts the page’s page_title