Molte aziende, prima di abbracciare integralmente l'approccio cloud preferiscono un approccio ibrido estendendo il proprio on-premise verso il cloud. Questa scelta aggiunge complessità nel monitoraggio e complica la gestione delle dashboard riassuntive sul funzionamento dell'infrastruttura. Durante la sessione verrà fatto un sintetico "state-of-art" dei principali strumenti per il monitoraggio arrivando poi a proporre un'architettura per il monitoraggio di infrastrutture ibride.

1. LA POTENZA È NULLA SENZA CONTROLLO
Giuliano Latini

3. #DOAW20
PERCHÉMISURARE?
• Per conoscere, descrivere, controllare qualsiasi sistema creando un
modello;
• L’azione di misurare quantifica e sintetizza una qualsiasi grandezza
materiale o immateriale con: uno o più numeri, una tabella
rappresentativa, un grafico che la mette in relazione con un’altra
grandezza;
• Quali sono i prerequisiti per fare una misura corretta?:
• Conoscere cosa intendiamo misurare;
• Comprendere l’unità di misura;
• Conoscere il comportamento della variabile da misurare;
• Accertarsi di avere la competenza adeguata e gli strumenti adatti per fare la misura;
• Conoscere il grado d’incertezza della misura e il numero di cifre significative dopo la
virgola.
• Misurare il sistema complesso rappresentato da un’infrastruttura ICT
permette di preventivare lo sforzo economico e di risorse necessario
all’erogazione dei servizi che ne giustificano l’esistenza.

4. #DOAW20
COSAMISURARE

5. #DOAW20
COSAMISURARE
• Anomalie;
• Errori;
• Analisi dei log files;
• Sensori dell’Hardware;
• Performance del Software;
• Tendenze di funzionamento.
Con lo scopo di:
• Essere avvertiti di possibili problemi (Alerting);
• Pianificare l’evoluzione dell’infrastruttura (Workload Management);
• Programmare l’infrastruttura per essere proattiva e resiliente su
problemi pre-classificati.

6. #DOAW20
SERIETEMPORALI
una serie storica (o temporale) si definisce come un insieme di variabili
casuali ordinate rispetto al tempo, ed esprime la dinamica di un certo
fenomeno nel tempo. Le serie storiche vengono studiate sia per
interpretare un fenomeno, individuando componenti di trend, di ciclicità,
di stagionalità e/o di accidentalità, sia per prevedere il suo andamento
futuro.

7. #DOAW20
HANDMADE-ARCHITETTURA

8. #DOAW20
NAGIOS-ARCHITETTURA
Time series DB stored as circular buffer

9. #DOAW20
NAGIOS

10. #DOAW20
ZABBIX-ARCHITETTURA
• Zabbix Server
• Zabbix Frontend
• Zabbix Agent
• Zabbix Proxy
• Protocolli
• SNMP
• IPMI
• JMX
• SSH
• Telnet
• Java gateway
• XMPP
• SMS
• DBMS Supported
• MySQL, PostgreSQL, Oracle, IBM DB2

11. #DOAW20
IBMTIVOLIMONITORING-ARCHITETTURA

12. #DOAW20
IBMTIVOLIMONITORING-ARCHITETTURA
• One or more Tivoli Enterprise Monitoring Servers, which act as a collection and control point for
alerts received from the agents, and collect their performance and availability data. The
monitoring server also manages the connection status of the agents. One server in each
environment must be designated as the hub.
• A Tivoli Enterprise Portal Server, which provides the core presentation layer for retrieval,
manipulation, analysis, and pre-formatting of data. The portal server retrieves data from the
hub monitoring server in response to user actions at the portal client, and sends the data back
to the portal client for presentation. The portal server also provides presentation information to
the portal client so that it can render the user interface views suitably.
• One or more Tivoli Enterprise Portal clients, with a Java-based user interface for viewing and
monitoring your enterprise. Tivoli Enterprise Portal offers two modes of operation: desktop and
browser.
• Tivoli Enterprise Monitoring Agents, installed on the systems or subsystems you want to
monitor. These agents collect data from monitored, or managed, systems and distribute this
information either to a monitoring server or to an EIF or SNMP event server such as
Netcool/OMNIbus.
• One or more instances of the tacmd Command Line Interface (CLI). This CLI is used to manage
your monitoring environment and can also be used to automate many of the administrative
functions performed using the Tivoli Enterprise Portal. The CLI commands either send requests
to the Hub monitoring server or to the Tivoli Enterprise Portal Server.

13. #DOAW20
MICROSOFTAZUREMONITOR

14. #DOAW20
MICROSOFTAZUREMONITORING-DASHBOARD

15. #DOAW20
STACKELK-ARCHITETTURA

16. #DOAW20
STACKELK-ARCHITETTURA

17. #DOAW20
STACKELK-FRONTEND

18. #DOAW20
STACKTICK-ARCHITETTURA

19. #DOAW20
STACKTICK-FRONTEND

20. #DOAW20
GRAFANA-ARCHITECTURE
• Dashboard
The dashboard is where it all comes together. A dashboard is a set of one or more panels organized
and arranged into one or more rows. Dashboards can use templating to make them more dynamic
and interactive. Dashboards can use annotations to display event data across panels. This can help
correlate the time series data in the panel with other events. Dashboards can be shared easily in a
variety of ways. Dashboards can be tagged, and the dashboard picker provides quick, searchable
access to all dashboards in a particular organization.
• Data source
Grafana can visualize, explore, and alert on data from many different databases and cloud services.
Each database or service type is accessed from a data source.Each data source has a specific query
editor that is customized for the features and capabilities that the particular data source exposes.
The query language and capabilities of each data source are obviously very different. You can
combine data from multiple data sources into a single dashboard, but each panel is connected to a
specific data source that belongs to a particular organization.
• Organization
Grafana supports multiple organizations in order to support a wide variety of deployment models,
including using a single Grafana instance to provide service to multiple potentially untrusted
organizations. In most cases, Grafana is deployed with a single organization. Each organization can
have one or more data sources. All dashboards are owned by a particular organization.

21. #DOAW20
GRAFANA-ARCHITECTURE
• Panel
The panel is the basic visualization building block in Grafana. Each panel has a Query Editor specific
to the data source selected in the panel. The query editor allows you to extract the perfect
visualization to display on the panel. Panels can be shared easily in a variety of ways.
• Query editor
The query editor exposes capabilities of your data source and allows you to query the metrics that
it contains. Use the query editor to build one or more queries in your time series database. The
panel instantly updates, allowing you to effectively explore your data in real time and build a
perfect query for that particular panel. You can use template variables in the query editor within
the queries themselves.
• Row
A row is a logical divider within a dashboard. It is used to group panels together. We use a unit
abstraction so that Grafana looks great on all screens sizes.
• User
A user is a named account in Grafana. A user can belong to one or more organizations and can be
assigned different levels of privileges through roles. Grafana supports a wide variety of internal and
external ways for users to authenticate themselves. These include from its own integrated
database, from an external SQL server, or from an external LDAP server.

22. #DOAW20
GRAFANA-FRONTEND

23. #DOAW20
PROMETHEUS-ARCHITETTURA

24. #DOAW20
PROMETHEUS-ARCHITETTURA

25. #DOAW20
PUSHVS.PULLBASEDMETRICS

26. #DOAW20
PROPOSTA1– USAREAZUREMONITOR

27. #DOAW20
PROPOSTA2–USAREGRAFANACOMEDATAFRONTEND
Telegraf
Azure Monitor plugin
Influxdb

28. #DOAW20
BIBLIOGRAFIA
• Nagios XI - Architecture Overview;
• Zabbix - Wikipedia;
• IBM Tivoli Monitoring;
• Microsoft Azure Monitor;
• ELK Stack: Elasticsearch, Logstash, Kibana | Elastic;
• Stack TICK;
• Grafana;
• Comparison to alternatives | Prometheus;
• Azure Monitor plugin for Grafana;
• Collecting Prometheus Metrics with Azure Monitor;
• Promitor - An Azure Monitor scraper for Prometheus;
• Collecting Prometheus Metrics with Azure Monitor | Runtime Configuration;
• Azure Monitor for containers with Prometheus now in preview | Microsoft Azure;
• Collect custom metrics for Linux VM with the InfluxData Telegraf agent - Azure Monitor;
• Telegraf Azure Monitor output plugin.

29. GRAZIEPERILVOSTROTEMPO
Giuliano Latini
latini.giuliano@gmail.com
about.me/giulianolatini
medium.com/@giulianolatini