Kafka 1.3.7. Redis 1.3.8. MQTT 1.3.9. Cassandra 1.3.10. MongoDB 1.3.11. Network socket 1.4. SLA (Service Level Agreement) 1.4.1. Checker 1.4.2. Alerters 2. Developer Guide 2.1. Architecture Collector 2.2.1. Event Driven Collector 2.2.2. Polled Collector 2.3. Custom Appender 2.4. Custom SLA Alerter 1. User Guide 1.1. Introduction Apache Karaf Decanter is monitoring solution running in given backend. Decanter provides appenders depending of the backend storage that you want to use. • SLA is a special kind of appender. It receives all harvested data and checks on it. If a check fails,

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524 3 SLA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -> Services) • Service actions - for service actions (new action type) • SLA - for configuring SLAs • SLA report - for SLA reports (also available as dashboard widget) Note that a separate section have problems • SLA is no longer a service attribute, but a separate entity which can be assigned to multiple services. During an upgrade, identical SLAs will be grouped and one SLA per each group will

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489 3 SLA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . the entire IT infrastructure service tree, identify weak places of the infrastructure, calculate SLA of various IT services, and check out other information at a higher level. Service monitoring focuses based on the statuses of child services. Services problem data can then be used to calculate SLA and send SLA reports based on the flexible set of conditions. Service monitoring is configured in the Services

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473 2 SLA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Define service actions for services with matching tags; • Use service tags to map a service to an SLA for SLA calculations. 12. Map services to problems using problem tags: • In the service configuration + Hosts + + + Latest data + + + Maps + + + Discovery + + Services + + + Services + + + SLA + + SLA report + + + Inventory + + + Overview + + + Hosts + + + Reports + + + System information

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512 3 服务级别协议 SLA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 用于服务概述和服务配置（从 Monitoring 移动到 Services） • 服务动作（Service actions） - 用于服务动作（新操作类型） • SLA - 用于配置 SLA • SLA 报表 - 用于 SLA 报表（也可用作仪表板小部件） 下面概述了对服务功能的其他主要改进。 基于标签的服务到问题的映射 以前版本中服务（services） 的可用性取决于触发器及其状态 -> Services) • Service actions - for service actions (new action type) • SLA - for configuring SLAs • SLA report - for SLA reports (also available as dashboard widget) 9 状态计算和传播规则 有新的状态计算规则和灵活的附

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476 2 SLA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Define service actions for services with matching tags; • Use service tags to map a service to an SLA for SLA calculations. 12. Map services to problems using problem tags: • In the service configuration + Hosts + + + Latest data + + + Maps + + + Discovery + + Services + + + Services + + + SLA + + SLA report + + + Inventory + + + Overview + + + Hosts + + + Reports + + + System information

mouseover (and a tooltip), reordered sla values, aligned by decimal point, removed graph ”show” link (now it’s on the bar, link to report is on the service name), expected sla shown in black not green, more would also be removed. Now the IT services are simply unlinked from the removed triggers and their SLA calculation disabled. Log file handling Zabbix agent startup log level was changed in order to log by our IT department. We can also be interested in identifying weak places of IT infrastructure, SLA of various IT services, the structure of existing IT infrastructure, and other information of a higher

provided by our IT department. We can also be interested in identifying weak places of IT infrastructure, SLA of various IT services, structure of existing IT infrastructure, and many other information of higher triggers. Warning: Note that triggers with severities Not classified and Information do not impact SLA calculation. Configuring IT Services To configure IT Services, go to Configuration → IT Services problem only if all child services are having problems Calculate SLA Enable SLA calculation and display. Acceptable SLA (in %) SLA percentage that is acceptable for this service. Used for reporting

by our IT department. We can also be interested in identifying weak places of IT infrastructure, SLA of various IT services, the structure of existing IT infrastructure, and other information of a higher their triggers. Note: Note that triggers with a Not classified or Information severity do not impact SLA calculation. Configuration To configure IT services, go to: Configuration → IT services. On this problem status, if all child services are having problems Calculate SLA Enable SLA calculation and display. Acceptable SLA (in %) SLA percentage that is acceptable for this service. Used for reporting

would also be removed. Now the IT services are simply unlinked from the removed triggers and their SLA calculation disabled. Log file handling Zabbix agent startup log level was changed in order to log by our IT department. We can also be interested in identifying weak places of IT infrastructure, SLA of various IT services, the structure of existing IT infrastructure, and other information of a higher their triggers. Note: Note that triggers with a Not classified or Information severity do not impact SLA calculation. Configuration To configure IT services, go to: Configuration → IT services. On this