Automated deployment of a microservice based monitoring architecture
-
Upload
augusto-ciuffoletti -
Category
Software
-
view
257 -
download
0
Transcript of Automated deployment of a microservice based monitoring architecture
![Page 1: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/1.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Cloud Forward 2015Automated deployment of a microservice-based
monitoring infrastructure
Augusto Ciuffoletti
6 ottobre 2015
![Page 2: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/2.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Introducing two topics
I The title:Automated deployment of a microservice-basedmonitoring infrastructure
I Microservices
I Monitoring on demand
Let us see how the two stories merge...
![Page 3: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/3.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Introducing two topics
I The title:Automated deployment of a microservice-basedmonitoring infrastructure
I Microservices
I Monitoring on demand
Let us see how the two stories merge...
![Page 4: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/4.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Introducing two topics
I The title:Automated deployment of a microservice-basedmonitoring infrastructure
I Microservices
I Monitoring on demand
Let us see how the two stories merge...
![Page 5: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/5.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Introducing two topics
I The title:Automated deployment of a microservice-basedmonitoring infrastructure
I Microservices
I Monitoring on demand
Let us see how the two stories merge...
![Page 6: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/6.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Number one: Microservices
I A design paradigm for distributed systemI a book in O’Reilly "animal series" by S Newman
I Principles:I each component in the system is designed to provide
one small, well defined serviceI each component is a stand alone entity that interacts
with others across a network with a well definedinterface
![Page 7: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/7.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Number one: Microservices
I A design paradigm for distributed systemI a book in O’Reilly "animal series" by S Newman
I Principles:I each component in the system is designed to provide
one small, well defined serviceI each component is a stand alone entity that interacts
with others across a network with a well definedinterface
![Page 8: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/8.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Number one: Microservices
I A design paradigm for distributed systemI a book in O’Reilly "animal series" by S Newman
I Principles:I each component in the system is designed to provide
one small, well defined serviceI each component is a stand alone entity that interacts
with others across a network with a well definedinterface
![Page 9: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/9.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Number one: Microservices
I A design paradigm for distributed systemI a book in O’Reilly "animal series" by S Newman
I Principles:I each component in the system is designed to provide
one small, well defined serviceI each component is a stand alone entity that interacts
with others across a network with a well definedinterface
![Page 10: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/10.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Number one: Microservices
I A design paradigm for distributed systemI a book in O’Reilly "animal series" by S Newman
I Principles:I each component in the system is designed to provide
one small, well defined serviceI each component is a stand alone entity that interacts
with others across a network with a well definedinterface
![Page 11: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/11.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Reasons to adopt the microservicesparadigm
I simplifies maintenanceI e.g., upgrade one single component
I agility in deploymentI e.g., to scale up or down
I each component may use a different technologyI e.g., for technical or performance reasons
I simplifies developmentI e.g., each component developed by a distinct team
I robustnessI e.g., if one component fails there is a chance that the
system still works
![Page 12: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/12.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Reasons to adopt the microservicesparadigm
I simplifies maintenanceI e.g., upgrade one single component
I agility in deploymentI e.g., to scale up or down
I each component may use a different technologyI e.g., for technical or performance reasons
I simplifies developmentI e.g., each component developed by a distinct team
I robustnessI e.g., if one component fails there is a chance that the
system still works
![Page 13: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/13.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Reasons to adopt the microservicesparadigm
I simplifies maintenanceI e.g., upgrade one single component
I agility in deploymentI e.g., to scale up or down
I each component may use a different technologyI e.g., for technical or performance reasons
I simplifies developmentI e.g., each component developed by a distinct team
I robustnessI e.g., if one component fails there is a chance that the
system still works
![Page 14: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/14.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Reasons to adopt the microservicesparadigm
I simplifies maintenanceI e.g., upgrade one single component
I agility in deploymentI e.g., to scale up or down
I each component may use a different technologyI e.g., for technical or performance reasons
I simplifies developmentI e.g., each component developed by a distinct team
I robustnessI e.g., if one component fails there is a chance that the
system still works
![Page 15: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/15.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Reasons to adopt the microservicesparadigm
I simplifies maintenanceI e.g., upgrade one single component
I agility in deploymentI e.g., to scale up or down
I each component may use a different technologyI e.g., for technical or performance reasons
I simplifies developmentI e.g., each component developed by a distinct team
I robustnessI e.g., if one component fails there is a chance that the
system still works
![Page 16: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/16.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Reasons to adopt the microservicesparadigm
I simplifies maintenanceI e.g., upgrade one single component
I agility in deploymentI e.g., to scale up or down
I each component may use a different technologyI e.g., for technical or performance reasons
I simplifies developmentI e.g., each component developed by a distinct team
I robustnessI e.g., if one component fails there is a chance that the
system still works
![Page 17: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/17.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Reasons to adopt the microservicesparadigm
I simplifies maintenanceI e.g., upgrade one single component
I agility in deploymentI e.g., to scale up or down
I each component may use a different technologyI e.g., for technical or performance reasons
I simplifies developmentI e.g., each component developed by a distinct team
I robustnessI e.g., if one component fails there is a chance that the
system still works
![Page 18: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/18.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Reasons to adopt the microservicesparadigm
I simplifies maintenanceI e.g., upgrade one single component
I agility in deploymentI e.g., to scale up or down
I each component may use a different technologyI e.g., for technical or performance reasons
I simplifies developmentI e.g., each component developed by a distinct team
I robustnessI e.g., if one component fails there is a chance that the
system still works
![Page 19: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/19.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Reasons to adopt the microservicesparadigm
I simplifies maintenanceI e.g., upgrade one single component
I agility in deploymentI e.g., to scale up or down
I each component may use a different technologyI e.g., for technical or performance reasons
I simplifies developmentI e.g., each component developed by a distinct team
I robustnessI e.g., if one component fails there is a chance that the
system still works
![Page 20: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/20.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Reasons to adopt the microservicesparadigm
I simplifies maintenanceI e.g., upgrade one single component
I agility in deploymentI e.g., to scale up or down
I each component may use a different technologyI e.g., for technical or performance reasons
I simplifies developmentI e.g., each component developed by a distinct team
I robustnessI e.g., if one component fails there is a chance that the
system still works
![Page 21: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/21.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Number two: Cloud monitoring
A cloud user wants to have a functional feedback fromcloud sourced resources:
I not necessarily to verify service qualityI control a scalable resource,I provide feedback to the users,I trigger compensating actions
I NIST indicates monitoring as one of the distinctivefeatures of cloud computing
![Page 22: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/22.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Number two: Cloud monitoring
A cloud user wants to have a functional feedback fromcloud sourced resources:
I not necessarily to verify service qualityI control a scalable resource,I provide feedback to the users,I trigger compensating actions
I NIST indicates monitoring as one of the distinctivefeatures of cloud computing
![Page 23: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/23.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Number two: Cloud monitoring
A cloud user wants to have a functional feedback fromcloud sourced resources:
I not necessarily to verify service qualityI control a scalable resource,I provide feedback to the users,I trigger compensating actions
I NIST indicates monitoring as one of the distinctivefeatures of cloud computing
![Page 24: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/24.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Number two: Cloud monitoring
A cloud user wants to have a functional feedback fromcloud sourced resources:
I not necessarily to verify service qualityI control a scalable resource,I provide feedback to the users,I trigger compensating actions
I NIST indicates monitoring as one of the distinctivefeatures of cloud computing
![Page 25: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/25.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Number two: Cloud monitoring
A cloud user wants to have a functional feedback fromcloud sourced resources:
I not necessarily to verify service qualityI control a scalable resource,I provide feedback to the users,I trigger compensating actions
I NIST indicates monitoring as one of the distinctivefeatures of cloud computing
![Page 26: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/26.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Number two: Cloud monitoring
A cloud user wants to have a functional feedback fromcloud sourced resources:
I not necessarily to verify service qualityI control a scalable resource,I provide feedback to the users,I trigger compensating actions
I NIST indicates monitoring as one of the distinctivefeatures of cloud computing
![Page 27: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/27.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Our option: on demand monitoring
I Provide monitoring as part of the serviceI Give the user wide possibilities to configure a
monitoring infrastructureI Which metrics are captured and how data are
preprocessed and retrievedI Scale from simple to complex infrastructures
I Do not overkill the problem in simple casesI Cope with complex infrastructures
I Resource agnosticI Basic functionalities and unlimited pluggable
extensions
![Page 28: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/28.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Our option: on demand monitoring
I Provide monitoring as part of the serviceI Give the user wide possibilities to configure a
monitoring infrastructureI Which metrics are captured and how data are
preprocessed and retrievedI Scale from simple to complex infrastructures
I Do not overkill the problem in simple casesI Cope with complex infrastructures
I Resource agnosticI Basic functionalities and unlimited pluggable
extensions
![Page 29: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/29.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Our option: on demand monitoring
I Provide monitoring as part of the serviceI Give the user wide possibilities to configure a
monitoring infrastructureI Which metrics are captured and how data are
preprocessed and retrievedI Scale from simple to complex infrastructures
I Do not overkill the problem in simple casesI Cope with complex infrastructures
I Resource agnosticI Basic functionalities and unlimited pluggable
extensions
![Page 30: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/30.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Our option: on demand monitoring
I Provide monitoring as part of the serviceI Give the user wide possibilities to configure a
monitoring infrastructureI Which metrics are captured and how data are
preprocessed and retrievedI Scale from simple to complex infrastructures
I Do not overkill the problem in simple casesI Cope with complex infrastructures
I Resource agnosticI Basic functionalities and unlimited pluggable
extensions
![Page 31: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/31.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Our option: on demand monitoring
I Provide monitoring as part of the serviceI Give the user wide possibilities to configure a
monitoring infrastructureI Which metrics are captured and how data are
preprocessed and retrievedI Scale from simple to complex infrastructures
I Do not overkill the problem in simple casesI Cope with complex infrastructures
I Resource agnosticI Basic functionalities and unlimited pluggable
extensions
![Page 32: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/32.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Our option: on demand monitoring
I Provide monitoring as part of the serviceI Give the user wide possibilities to configure a
monitoring infrastructureI Which metrics are captured and how data are
preprocessed and retrievedI Scale from simple to complex infrastructures
I Do not overkill the problem in simple casesI Cope with complex infrastructures
I Resource agnosticI Basic functionalities and unlimited pluggable
extensions
![Page 33: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/33.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Our option: on demand monitoring
I Provide monitoring as part of the serviceI Give the user wide possibilities to configure a
monitoring infrastructureI Which metrics are captured and how data are
preprocessed and retrievedI Scale from simple to complex infrastructures
I Do not overkill the problem in simple casesI Cope with complex infrastructures
I Resource agnosticI Basic functionalities and unlimited pluggable
extensions
![Page 34: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/34.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Our option: on demand monitoring
I Provide monitoring as part of the serviceI Give the user wide possibilities to configure a
monitoring infrastructureI Which metrics are captured and how data are
preprocessed and retrievedI Scale from simple to complex infrastructures
I Do not overkill the problem in simple casesI Cope with complex infrastructures
I Resource agnosticI Basic functionalities and unlimited pluggable
extensions
![Page 35: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/35.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Find a match
I Monitoring is by nature split into small components(remember Nagios)
I monitoring probes are small components, possiblyembedded
I monitoring data crosses a pipe of processors(anonymization, aggregation etc)
I data is finally published using an endpoint reachablefrom the outside (database, web service)
I Each component is supported by a specifictechnology
I e.g., network monitoring vs storage monitoringI The on demand nature requires agility in deployment
I the cloud user that obtains a new resource may wantto monitor it
There is a match betweenmicroservices and on demand monitoring
![Page 36: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/36.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Find a match
I Monitoring is by nature split into small components(remember Nagios)
I monitoring probes are small components, possiblyembedded
I monitoring data crosses a pipe of processors(anonymization, aggregation etc)
I data is finally published using an endpoint reachablefrom the outside (database, web service)
I Each component is supported by a specifictechnology
I e.g., network monitoring vs storage monitoringI The on demand nature requires agility in deployment
I the cloud user that obtains a new resource may wantto monitor it
There is a match betweenmicroservices and on demand monitoring
![Page 37: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/37.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Find a match
I Monitoring is by nature split into small components(remember Nagios)
I monitoring probes are small components, possiblyembedded
I monitoring data crosses a pipe of processors(anonymization, aggregation etc)
I data is finally published using an endpoint reachablefrom the outside (database, web service)
I Each component is supported by a specifictechnology
I e.g., network monitoring vs storage monitoringI The on demand nature requires agility in deployment
I the cloud user that obtains a new resource may wantto monitor it
There is a match betweenmicroservices and on demand monitoring
![Page 38: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/38.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Find a match
I Monitoring is by nature split into small components(remember Nagios)
I monitoring probes are small components, possiblyembedded
I monitoring data crosses a pipe of processors(anonymization, aggregation etc)
I data is finally published using an endpoint reachablefrom the outside (database, web service)
I Each component is supported by a specifictechnology
I e.g., network monitoring vs storage monitoringI The on demand nature requires agility in deployment
I the cloud user that obtains a new resource may wantto monitor it
There is a match betweenmicroservices and on demand monitoring
![Page 39: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/39.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Find a match
I Monitoring is by nature split into small components(remember Nagios)
I monitoring probes are small components, possiblyembedded
I monitoring data crosses a pipe of processors(anonymization, aggregation etc)
I data is finally published using an endpoint reachablefrom the outside (database, web service)
I Each component is supported by a specifictechnology
I e.g., network monitoring vs storage monitoringI The on demand nature requires agility in deployment
I the cloud user that obtains a new resource may wantto monitor it
There is a match betweenmicroservices and on demand monitoring
![Page 40: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/40.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Find a match
I Monitoring is by nature split into small components(remember Nagios)
I monitoring probes are small components, possiblyembedded
I monitoring data crosses a pipe of processors(anonymization, aggregation etc)
I data is finally published using an endpoint reachablefrom the outside (database, web service)
I Each component is supported by a specifictechnology
I e.g., network monitoring vs storage monitoringI The on demand nature requires agility in deployment
I the cloud user that obtains a new resource may wantto monitor it
There is a match betweenmicroservices and on demand monitoring
![Page 41: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/41.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Find a match
I Monitoring is by nature split into small components(remember Nagios)
I monitoring probes are small components, possiblyembedded
I monitoring data crosses a pipe of processors(anonymization, aggregation etc)
I data is finally published using an endpoint reachablefrom the outside (database, web service)
I Each component is supported by a specifictechnology
I e.g., network monitoring vs storage monitoringI The on demand nature requires agility in deployment
I the cloud user that obtains a new resource may wantto monitor it
There is a match betweenmicroservices and on demand monitoring
![Page 42: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/42.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Find a match
I Monitoring is by nature split into small components(remember Nagios)
I monitoring probes are small components, possiblyembedded
I monitoring data crosses a pipe of processors(anonymization, aggregation etc)
I data is finally published using an endpoint reachablefrom the outside (database, web service)
I Each component is supported by a specifictechnology
I e.g., network monitoring vs storage monitoringI The on demand nature requires agility in deployment
I the cloud user that obtains a new resource may wantto monitor it
There is a match betweenmicroservices and on demand monitoring
![Page 43: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/43.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Find a match
I Monitoring is by nature split into small components(remember Nagios)
I monitoring probes are small components, possiblyembedded
I monitoring data crosses a pipe of processors(anonymization, aggregation etc)
I data is finally published using an endpoint reachablefrom the outside (database, web service)
I Each component is supported by a specifictechnology
I e.g., network monitoring vs storage monitoringI The on demand nature requires agility in deployment
I the cloud user that obtains a new resource may wantto monitor it
There is a match betweenmicroservices and on demand monitoring
![Page 44: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/44.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Summarizing: a IaaS provisioning
I IaaS is just for the example: could be PaaS oranything else
![Page 45: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/45.jpg)
Cloud Forward2015
Augusto Ciuffoletti
A monitoring infrastructure
I Adding a monitoring infrastructure:I probes that collect monitoring data (collectors)I a device that processes monitoring data (sensor)
![Page 46: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/46.jpg)
Cloud Forward2015
Augusto Ciuffoletti
A monitoring infrastructure
I Adding a monitoring infrastructure:I probes that collect monitoring data (collectors)I a device that processes monitoring data (sensor)
![Page 47: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/47.jpg)
Cloud Forward2015
Augusto Ciuffoletti
A monitoring infrastructure
I Adding a monitoring infrastructure:I probes that collect monitoring data (collectors)I a device that processes monitoring data (sensor)
![Page 48: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/48.jpg)
Cloud Forward2015
Augusto Ciuffoletti
A cloud interface
I we need to design an interfaceI an open standard exists: OCCI
![Page 49: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/49.jpg)
Cloud Forward2015
Augusto Ciuffoletti
A cloud interface
I we need to design an interfaceI an open standard exists: OCCI
![Page 50: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/50.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Open Cloud Computing Interface basics
I The interface is REST, therefore web-orientedI The items accessed across the interface are entitiesI One type of entity is the resourceI Another is the link, that connects two resourcesI A type is characterized by standard features of the
instancesI attributes whose values define instancesI actions that model dynamic change
I The interface is extensible:I a type can be subtyped, thus adding new attributes
to the standard onesI an instance can be modified using mixins
![Page 51: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/51.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Open Cloud Computing Interface basics
I The interface is REST, therefore web-orientedI The items accessed across the interface are entitiesI One type of entity is the resourceI Another is the link, that connects two resourcesI A type is characterized by standard features of the
instancesI attributes whose values define instancesI actions that model dynamic change
I The interface is extensible:I a type can be subtyped, thus adding new attributes
to the standard onesI an instance can be modified using mixins
![Page 52: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/52.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Open Cloud Computing Interface basics
I The interface is REST, therefore web-orientedI The items accessed across the interface are entitiesI One type of entity is the resourceI Another is the link, that connects two resourcesI A type is characterized by standard features of the
instancesI attributes whose values define instancesI actions that model dynamic change
I The interface is extensible:I a type can be subtyped, thus adding new attributes
to the standard onesI an instance can be modified using mixins
![Page 53: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/53.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Open Cloud Computing Interface basics
I The interface is REST, therefore web-orientedI The items accessed across the interface are entitiesI One type of entity is the resourceI Another is the link, that connects two resourcesI A type is characterized by standard features of the
instancesI attributes whose values define instancesI actions that model dynamic change
I The interface is extensible:I a type can be subtyped, thus adding new attributes
to the standard onesI an instance can be modified using mixins
![Page 54: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/54.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Open Cloud Computing Interface basics
I The interface is REST, therefore web-orientedI The items accessed across the interface are entitiesI One type of entity is the resourceI Another is the link, that connects two resourcesI A type is characterized by standard features of the
instancesI attributes whose values define instancesI actions that model dynamic change
I The interface is extensible:I a type can be subtyped, thus adding new attributes
to the standard onesI an instance can be modified using mixins
![Page 55: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/55.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Open Cloud Computing Interface basics
I The interface is REST, therefore web-orientedI The items accessed across the interface are entitiesI One type of entity is the resourceI Another is the link, that connects two resourcesI A type is characterized by standard features of the
instancesI attributes whose values define instancesI actions that model dynamic change
I The interface is extensible:I a type can be subtyped, thus adding new attributes
to the standard onesI an instance can be modified using mixins
![Page 56: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/56.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Open Cloud Computing Interface basics
I The interface is REST, therefore web-orientedI The items accessed across the interface are entitiesI One type of entity is the resourceI Another is the link, that connects two resourcesI A type is characterized by standard features of the
instancesI attributes whose values define instancesI actions that model dynamic change
I The interface is extensible:I a type can be subtyped, thus adding new attributes
to the standard onesI an instance can be modified using mixins
![Page 57: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/57.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Open Cloud Computing Interface basics
I The interface is REST, therefore web-orientedI The items accessed across the interface are entitiesI One type of entity is the resourceI Another is the link, that connects two resourcesI A type is characterized by standard features of the
instancesI attributes whose values define instancesI actions that model dynamic change
I The interface is extensible:I a type can be subtyped, thus adding new attributes
to the standard onesI an instance can be modified using mixins
![Page 58: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/58.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Open Cloud Computing Interface basics
I The interface is REST, therefore web-orientedI The items accessed across the interface are entitiesI One type of entity is the resourceI Another is the link, that connects two resourcesI A type is characterized by standard features of the
instancesI attributes whose values define instancesI actions that model dynamic change
I The interface is extensible:I a type can be subtyped, thus adding new attributes
to the standard onesI an instance can be modified using mixins
![Page 59: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/59.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Open Cloud Computing Interface basics
I The interface is REST, therefore web-orientedI The items accessed across the interface are entitiesI One type of entity is the resourceI Another is the link, that connects two resourcesI A type is characterized by standard features of the
instancesI attributes whose values define instancesI actions that model dynamic change
I The interface is extensible:I a type can be subtyped, thus adding new attributes
to the standard onesI an instance can be modified using mixins
![Page 60: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/60.jpg)
Cloud Forward2015
Augusto Ciuffoletti
An OCCI model for monitoring
I A Sensor is a subtype of the Resource typeI A Collector is a subtype of the Link typeI Add Mixins to specify the type of activity
I Legenda:I the sensor (red) is an OCCI resourceI the collectors (blue) are OCCI linksI computing boxes and the network are OCCI
resources too
![Page 61: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/61.jpg)
Cloud Forward2015
Augusto Ciuffoletti
An OCCI model for monitoring
I A Sensor is a subtype of the Resource typeI A Collector is a subtype of the Link typeI Add Mixins to specify the type of activity
I Legenda:I the sensor (red) is an OCCI resourceI the collectors (blue) are OCCI linksI computing boxes and the network are OCCI
resources too
![Page 62: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/62.jpg)
Cloud Forward2015
Augusto Ciuffoletti
An OCCI model for monitoring
I A Sensor is a subtype of the Resource typeI A Collector is a subtype of the Link typeI Add Mixins to specify the type of activity
I Legenda:I the sensor (red) is an OCCI resourceI the collectors (blue) are OCCI linksI computing boxes and the network are OCCI
resources too
![Page 63: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/63.jpg)
Cloud Forward2015
Augusto Ciuffoletti
An OCCI model for monitoring
I A Sensor is a subtype of the Resource typeI A Collector is a subtype of the Link typeI Add Mixins to specify the type of activity
I Legenda:I the sensor (red) is an OCCI resourceI the collectors (blue) are OCCI linksI computing boxes and the network are OCCI
resources too
![Page 64: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/64.jpg)
Cloud Forward2015
Augusto Ciuffoletti
An OCCI model for monitoring
I A Sensor is a subtype of the Resource typeI A Collector is a subtype of the Link typeI Add Mixins to specify the type of activity
I Legenda:I the sensor (red) is an OCCI resourceI the collectors (blue) are OCCI linksI computing boxes and the network are OCCI
resources too
![Page 65: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/65.jpg)
Cloud Forward2015
Augusto Ciuffoletti
An OCCI model for monitoring
I A Sensor is a subtype of the Resource typeI A Collector is a subtype of the Link typeI Add Mixins to specify the type of activity
I Legenda:I the sensor (red) is an OCCI resourceI the collectors (blue) are OCCI linksI computing boxes and the network are OCCI
resources too
![Page 66: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/66.jpg)
Cloud Forward2015
Augusto Ciuffoletti
An OCCI model for monitoring
I A Sensor is a subtype of the Resource typeI A Collector is a subtype of the Link typeI Add Mixins to specify the type of activity
I Legenda:I the sensor (red) is an OCCI resourceI the collectors (blue) are OCCI linksI computing boxes and the network are OCCI
resources too
![Page 67: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/67.jpg)
Cloud Forward2015
Augusto Ciuffoletti
An OCCI model for monitoring
I A Sensor is a subtype of the Resource typeI A Collector is a subtype of the Link typeI Add Mixins to specify the type of activity
I Legenda:I the sensor (red) is an OCCI resourceI the collectors (blue) are OCCI linksI computing boxes and the network are OCCI
resources too
![Page 68: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/68.jpg)
Cloud Forward2015
Augusto Ciuffoletti
How do we do that?
I We want to study the big arrow in the figureHow do we implement a monitoring infrastructure starting
form OCCI entities
![Page 69: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/69.jpg)
Cloud Forward2015
Augusto Ciuffoletti
How do we do that?
I We want to study the big arrow in the figureHow do we implement a monitoring infrastructure starting
form OCCI entities
![Page 70: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/70.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Vintage programming but...
I For an early prototype we selected seasonedtechnologies: Java/Unix sockets/Unix Pipes
I not bound to specific programming toolsI better solutions do exist
I As a virtualization platform we selected DockerI demo is easely reproduceable/shareableI efficient to run on a single laptopI upgradeable to a real deployment
![Page 71: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/71.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Vintage programming but...
I For an early prototype we selected seasonedtechnologies: Java/Unix sockets/Unix Pipes
I not bound to specific programming toolsI better solutions do exist
I As a virtualization platform we selected DockerI demo is easely reproduceable/shareableI efficient to run on a single laptopI upgradeable to a real deployment
![Page 72: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/72.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Vintage programming but...
I For an early prototype we selected seasonedtechnologies: Java/Unix sockets/Unix Pipes
I not bound to specific programming toolsI better solutions do exist
I As a virtualization platform we selected DockerI demo is easely reproduceable/shareableI efficient to run on a single laptopI upgradeable to a real deployment
![Page 73: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/73.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Vintage programming but...
I For an early prototype we selected seasonedtechnologies: Java/Unix sockets/Unix Pipes
I not bound to specific programming toolsI better solutions do exist
I As a virtualization platform we selected DockerI demo is easely reproduceable/shareableI efficient to run on a single laptopI upgradeable to a real deployment
![Page 74: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/74.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Vintage programming but...
I For an early prototype we selected seasonedtechnologies: Java/Unix sockets/Unix Pipes
I not bound to specific programming toolsI better solutions do exist
I As a virtualization platform we selected DockerI demo is easely reproduceable/shareableI efficient to run on a single laptopI upgradeable to a real deployment
![Page 75: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/75.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Vintage programming but...
I For an early prototype we selected seasonedtechnologies: Java/Unix sockets/Unix Pipes
I not bound to specific programming toolsI better solutions do exist
I As a virtualization platform we selected DockerI demo is easely reproduceable/shareableI efficient to run on a single laptopI upgradeable to a real deployment
![Page 76: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/76.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Vintage programming but...
I For an early prototype we selected seasonedtechnologies: Java/Unix sockets/Unix Pipes
I not bound to specific programming toolsI better solutions do exist
I As a virtualization platform we selected DockerI demo is easely reproduceable/shareableI efficient to run on a single laptopI upgradeable to a real deployment
![Page 77: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/77.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Deploying a demo infrastructure
I The minimal architecture (4 dockers):I one HTTP server to host the OCCI entities
descriptionsI one dashboard to display monitoring dataI one monitored compute resourceI one sensor resource
I In OCCI viewI One compute resourceI One sensor resourceI One collector link
![Page 78: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/78.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Deploying a demo infrastructure
I The minimal architecture (4 dockers):I one HTTP server to host the OCCI entities
descriptionsI one dashboard to display monitoring dataI one monitored compute resourceI one sensor resource
I In OCCI viewI One compute resourceI One sensor resourceI One collector link
![Page 79: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/79.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Deploying a demo infrastructure
I The minimal architecture (4 dockers):I one HTTP server to host the OCCI entities
descriptionsI one dashboard to display monitoring dataI one monitored compute resourceI one sensor resource
I In OCCI viewI One compute resourceI One sensor resourceI One collector link
![Page 80: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/80.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Deploying a demo infrastructure
I The minimal architecture (4 dockers):I one HTTP server to host the OCCI entities
descriptionsI one dashboard to display monitoring dataI one monitored compute resourceI one sensor resource
I In OCCI viewI One compute resourceI One sensor resourceI One collector link
![Page 81: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/81.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Deploying a demo infrastructure
I The minimal architecture (4 dockers):I one HTTP server to host the OCCI entities
descriptionsI one dashboard to display monitoring dataI one monitored compute resourceI one sensor resource
I In OCCI viewI One compute resourceI One sensor resourceI One collector link
![Page 82: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/82.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Deploying a demo infrastructure
I The minimal architecture (4 dockers):I one HTTP server to host the OCCI entities
descriptionsI one dashboard to display monitoring dataI one monitored compute resourceI one sensor resource
I In OCCI viewI One compute resourceI One sensor resourceI One collector link
![Page 83: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/83.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Deploying a demo infrastructure
I The minimal architecture (4 dockers):I one HTTP server to host the OCCI entities
descriptionsI one dashboard to display monitoring dataI one monitored compute resourceI one sensor resource
I In OCCI viewI One compute resourceI One sensor resourceI One collector link
![Page 84: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/84.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Deploying a demo infrastructure
I The minimal architecture (4 dockers):I one HTTP server to host the OCCI entities
descriptionsI one dashboard to display monitoring dataI one monitored compute resourceI one sensor resource
I In OCCI viewI One compute resourceI One sensor resourceI One collector link
![Page 85: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/85.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Deploying a demo infrastructure
I The minimal architecture (4 dockers):I one HTTP server to host the OCCI entities
descriptionsI one dashboard to display monitoring dataI one monitored compute resourceI one sensor resource
I In OCCI viewI One compute resourceI One sensor resourceI One collector link
![Page 86: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/86.jpg)
Cloud Forward2015
Augusto Ciuffoletti
The web server
I The web server is deployed (with OCCI docs)I this is part of the cloud infrastructure
![Page 87: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/87.jpg)
Cloud Forward2015
Augusto Ciuffoletti
The web server
I The web server is deployed (with OCCI docs)I this is part of the cloud infrastructure
![Page 88: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/88.jpg)
Cloud Forward2015
Augusto Ciuffoletti
The dashboard
I The dashboard is deployed (UDP to receive data)I this is on user premises
![Page 89: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/89.jpg)
Cloud Forward2015
Augusto Ciuffoletti
The dashboard
I The dashboard is deployed (UDP to receive data)I this is on user premises
![Page 90: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/90.jpg)
Cloud Forward2015
Augusto Ciuffoletti
The computing resource
I The virtual computing resource is deployedI the RMI interface is for configuration
![Page 91: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/91.jpg)
Cloud Forward2015
Augusto Ciuffoletti
The computing resource
I The virtual computing resource is deployedI the RMI interface is for configuration
![Page 92: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/92.jpg)
Cloud Forward2015
Augusto Ciuffoletti
The sensor
I It is the resource that implements the monitoringI uploads the collector across the RMI interface
![Page 93: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/93.jpg)
Cloud Forward2015
Augusto Ciuffoletti
The sensor
I It is the resource that implements the monitoringI uploads the collector across the RMI interface
![Page 94: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/94.jpg)
Cloud Forward2015
Augusto Ciuffoletti
GO!
I The dashboard receives the probe measurements...I ...filtered by the sensor
![Page 95: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/95.jpg)
Cloud Forward2015
Augusto Ciuffoletti
GO!
I The dashboard receives the probe measurements...I ...filtered by the sensor
![Page 96: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/96.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Conclusions
I Microservices are appropriate for distributedmonitoring
I The OCCI API is appropriate as the interfaceI A prototype is available on dockerhub (look for
occimon-live)I BYOD demo on stage tonight at 17:45
![Page 97: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/97.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Conclusions
I Microservices are appropriate for distributedmonitoring
I The OCCI API is appropriate as the interfaceI A prototype is available on dockerhub (look for
occimon-live)I BYOD demo on stage tonight at 17:45
![Page 98: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/98.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Conclusions
I Microservices are appropriate for distributedmonitoring
I The OCCI API is appropriate as the interfaceI A prototype is available on dockerhub (look for
occimon-live)I BYOD demo on stage tonight at 17:45
![Page 99: Automated deployment of a microservice based monitoring architecture](https://reader031.fdocuments.net/reader031/viewer/2022030402/5881bd661a28abdd268b45d7/html5/thumbnails/99.jpg)
Cloud Forward2015
Augusto Ciuffoletti
Conclusions
I Microservices are appropriate for distributedmonitoring
I The OCCI API is appropriate as the interfaceI A prototype is available on dockerhub (look for
occimon-live)I BYOD demo on stage tonight at 17:45