[OASIS Issue Tracker] (TOSCA-216) General Issues for Monitoring Ad Hoc Group

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/TOSCA-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55950#comment-55950 ] 

Chip Holden commented on TOSCA-216:
-----------------------------------

Response from Yaron:

I want to say that we think that while it might be true that a metric should be a capability of a Node, we don’t like the idea of metric and metric group being nodes in the topology nor a node type  (which opens the door to the question whether capability always point to a node)

We think that the role of a node template is to represent a component in the application. A metric is definitely not a component in the application. Furthermore, there can be some types of application servers and database servers that will report dozens of metrics. This will make the topology and blueprint impossible to read and visualize

We think it is taking TOSCA to the wrong path.

We can think about several possibilities:

Metrics being properties of a monitoring intrerface
Metrics being properties of a monitoring agent or collector, that is a node template in the application topology
Metrics being part of a dedicated new monitoring section

> General Issues for Monitoring Ad Hoc Group 
> -------------------------------------------
>
>                 Key: TOSCA-216
>                 URL: https://issues.oasis-open.org/browse/TOSCA-216
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Monitoring
>            Reporter: Paul Lipton 
>            Assignee: Chip Holden
>




--
This message was sent by Atlassian JIRA
(v6.2.2#6258)