Publication rules¶
You can define several publication rules for the same report generated by a job. The available publication methods are the following:
local : to publish reports on the reporting server
CIFS : to publish reports on a windows share folder
FTP : to publish reports on a remote FTP server
SFTP : to publish reports on another Linux/Unix server via SSH
SMTP : to publish reports by e-mail
DropBox : To publish reports on a DropBox account
The publication rules are defined in the menu:
Reports > Business Intelligence > Publication rules
Rules list¶
Description of the columns:
Column |
Description |
|---|---|
Name |
Name of the publication rule |
Protocol |
Protocol used to publish the reports |
Global |
A global publication rule is applied to each report generated by Centreon MBI. A rule that is not global must be linked to a job in order to be effective for the reports generated by this job |
Description |
Description of the rule |
Options |
Number of the times that the rule will be duplicated if the option « Duplicate » is selected in the menu « More actions » |
The “Default” publication rule can’t be deleted or renamed. The protocol used in this rule must be configured in order to be able to access the reports from the menu:
Reporting > Business Intelligence > Archives
Add/Edit¶
You can add or edit report publication rules. The different protocols have common and specific parameters.
Description of the common parameters:
Column |
Description |
|---|---|
Name |
Name of the publication rule |
Protocol |
Protocol used to publish the reports |
Global |
A global publication rule is applied to each report generated by Centreon MBI. A rule that is not global must be linked to a job in order to be effective for the reports generated by this job |
Description |
Description of the rule |
Root directory |
Report parent storage folder |
Sub directory |
In order to organize the generated reports, a sub-directory can be generated based on variables initialized at the report publication time. The table bellow describes the different variables that could be used in this field |
Variables that could be used in the sub directory definition:
Variable |
Description |
|---|---|
@DAY@ |
Day of month when the report is published |
@MONTH@ |
Month of the year when the report is published |
@YEAR@ |
Year of the report publication |
@PUBLICATIONDATE@ |
Date of the report publication. Date format : « YYYYMMDD » |
@PUBLICATIONDATETIME@ |
Date and time of the report publication. Format : « YYYYMMDDHi » (« H » defines the hours and « i » defines the minutes) |
@JOBNAME@ |
Name of the report generation job |
@REPORTMODELNAME@ |
Name of the report model |
Sub directory example:
@REPORTMODELNAME@/JOBNAME@/@PUBLICATIONDATE@
Mail publication specificities (SMTP)¶
It is possible to specify a maximum size for the report to be sent by mail with the parameter “Maximum report size”. If the report’ size exceeds the parameter, a link will be generated.
Some specific behaviour have to be understood because of the link between SMTP publication and Centreon MBI’ACL. To give access to reports or jobs to a non-admin user, you have to define specific Centreon MBI rules. Please refer to this chapter to learn how to create and manage Centreon MBI rules: Access restrictions (ACL).
The rules applied to the mail publication are explained below :
Case 1 - User = Administrator
The user belongs at least to one contact group linked to the publication rule
The user is admin
Case 2 - User ∈ Contacts Group(s) ∈ Access Group(s) ∈ ACL Rules
The user belongs at least to one contact group linked to the publication rule
The contacts group(s) associated to the user are in one or more access groups, these groups are associated to one or more ACL rule(s). This(these) rules are at least linked 1 time to the job concerned, no matter if the ACL rule is linked to the job group or the job.
Case 3 - User ∈ Access Group(s) ∈ ACL Rule(s)
The user belongs at least to one contact group associated to the publication rule
The user is directly linked at least to one access group(s) and this(these) access group(s) are linked at least to one or more ACL rule(s). This(these) rules are at least linked 1 time to the job concerned, no matter if the ACL rule is linked to the job group or the job.
Global
If a user belongs to many ACL rules, it is the union of these rules that defines if the reports is sent or not <=> If at least one path exists between the job and the user, he will receive the mail.