Skip to content

Conversation

bourretp
Copy link
Contributor

Resolve #155 (Add Monitoring Support)

Monitoring templates can be dropped in the Roboconf configuration directory:

  • either in the monitoring-template directory, in this case the template is global to all applications.
  • or in the {applicationName}/monitoring-template directory, in this case the template is specific to that application.

The templates use a {{mustache}} based syntax, extended with Handlebars features + Roboconf specific operators (helpers).
See the Roboconf Specification Request 232 (Monitoring Template Language) for a complete description of the template syntax.
The monitoring reports output syntax can be virtually anything (text-based).

The monitoring manager scans the Roboconf configuration directory for changes in the templates. If a template is added/modified,
the corresponding monitoring reports is generated/updated. Reports are not removed whan a template has gone.

The monitoring part is optional: it means the Roboconf DM can work perfectly without the presence of the monitoring manager bundle.

Monitoring templates can be dropped in the Roboconf configuration directory:
- either in the monitoring-template directory, in this case the template is global to all applications.
- or in the {applicationName}/monitoring-template directory, in this case the template is specific to that application.

The templates use a {{mustache}} based syntax, extended with Handlebars features + Roboconf specific operators (helpers).
See the Roboconf Specification Request 232 (Monitoring Template Language) for a complete description of the template syntax.
The monitoring reports output syntax can be virtually anything (text-based).

The monitoring manager scans the Roboconf configuration directory for changes in the templates. If a template is added/modified,
the corresponding monitoring reports is generated/updated. Reports are *not* removed whan a template has gone.

The monitoring part is *optional*: it means the Roboconf DM can work perfectly without the presence of the monitoring manager bundle.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Following our discussion this morning, should it be called "monitoring"?
Templates seems more suitable now. WDT?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest to leave it as is for now, until we find other usages for the templates.

@vincent-zurczak
Copy link
Member

The Travis build failed, but it builds perfectly on my machine.

vincent-zurczak added a commit that referenced this pull request Apr 28, 2015
@vincent-zurczak vincent-zurczak merged commit 310c225 into roboconf:master Apr 28, 2015
@bourretp bourretp deleted the feature/dm-monitoring-rebase branch April 29, 2015 12:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add Monitoring Support

3 participants