3 KEY ELEMENTS FOR YOUR GITOPS STRATEGY Copyright 2024 Akamai Technologies. All rights reserved. Any trademarked names and logos are property of their respective companies. EBOOK GITOPS 3 KEY ELEMENTS . . . . . . . . . . . . . . . . . . . . . 12 | 03 3 KEY ELEMENTS FOR YOUR GITOPS STRATEGY Copyright 2024 Akamai Technologies. All rights reserved. Any trademarked philosophy of GitOps, what your current deployment strategy looks like, and essential tools are key to implementing a successful GitOps strategy. In this ebook you will learn: • a refresher on the

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614 1 Virtual machine discovery key fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619 11 information. This item can be used for the discovery of IPMI sensors. Item key limit raised The maximum allowed length of an item key has been raised from 256 to 2048 characters. Extended range of numeric option specifies that each line of the input file contains the following, whitespace-delimited: <key> , e.g.: Zabbix server" trap001 1429533600 748744024 43 Zabbix server" trap001

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573 1 Virtual machine discovery key fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578 11 privacy passphrases, passwords for media types; SSL key password and HTTP proxy fields used in web scenarios and HTTP items; usernames, passwords and key passphrases in remote commands. This setting shall partitions Updated macros • {ITEM.KEY.ORIG} macro is now supported in HTTP agent type and Script type items, item prototypes, and discovery rules; • {ITEM.ID} and {ITEM.KEY} macros are now supported in Script

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500 1 Virtual machine discovery key fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504 11 devices Low-level discovery of block devices and their type is supported using a new built-in discovery key: vfs.dev.discovery The discovery will return a JSON with the values of two macros - {#DEVNAME} and units (services, by default) is supported using a new built-in discovery key: systemd.unit.discovery Attention: This item key is only supported in Zabbix agent 2. The discovery will return a JSON with

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479 1 Virtual machine discovery key fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484 11 filter. Two more new options are available in the problem filter: • Highlight whole row allows to highlight the full row of unresolved problems using the problem severity color. This option is available Keyboard navigation • All interactive elements (except maps) can now be accessed by pressing the Tab key; • Popups can now be opened, worked with and closed by keyboard; • Context menu options can now be

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467 1 Virtual machine discovery key fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471 11 longer expected that the JSON will contain the ”data” object: { "data": [ {row>}, {row>} ] } Low-level discovery will now accept a normal JSON containing an array. Built-in discovery Zabbix will automatically extract a macro and value if an array field uses the {#MACRO} syntax as a key. Any new native discovery checks will use the new syntax without the ”data” elements. When processing

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594 1 Virtual machine discovery key fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599 11 easier to use • Item sets for aggregation can be specified using complex filters referencing the item key, host group and tags • The new syntax supports other expressions as parameters • Item reference is server/tick,3m)=1 {Zabbix server:tick.nodata(3m)}=1 A simple trigger expression min(min(/host/key,1h),min(/host2/key2,1h)*10,#20) Not available/supported Using other expressions as function parameters (referencing

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517 Virtual machine discovery key fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532 JSON data[key,] - return data for the specified value name in the Windows Registry key • registry.get[key,,] - list of Windows Registry values or keys located at given key; returns total availability is gray (unknown) Additionally, active agent availability is listed, as a separate row, in the popup list of available agent interfaces. This popup is opened when hovering over the host

properly distinguish between the RFC2616 HTTP/1.1 caching features provided by mod_cache, and the generic key/value caching provided by the socache interface, as well as to cover specialised caching provided by on a potentially slow disk. Two-state key/value shared object caching The shared object cache API (socache) and its provider modules provide a server wide key/value based shared object cache. These modules RFC2616, and the mod_cache module can be used to take advantage of this. Unlike a simple two state key/value cache where the content disappears completely when no longer fresh, an HTTP cache includes a

properly distinguish between the RFC2616 HTTP/1.1 caching features provided by mod_cache, and the generic key/value caching provided by the socache interface, as well as to cover specialised caching provided by on a potentially slow disk. Two-state key/value shared object caching The shared object cache API (socache) and its provider modules provide a server wide key/value based shared object cache. These modules RFC2616, and the mod_cache module can be used to take advantage of this. Unlike a simple two state key/value cache where the content disappears completely when no longer fresh, an HTTP cache includes a