Configuration

ACLs

When you first install Map 4, only Centreon Web administrators can set ACLs.

Map 4 handle ACLs by ACL groups, defined in Centreon Web. You cannot set ACL user by user.

Add / remove new administrators

You can decide which ACL group is a Map 4 administrator.

Go into Preferences -> Preferences then select Admin

All ACL groups from Centreon Web are displayed here and you can decide weather they are Centreon administrators or not.

../../_images/admin_preference_page.png

Give specific rights to some users

You can allow ACL groups to create, modify or delete views directly from your desktop client.

Go into Preferences -> Preferences then select Views -> ACLs

../../_images/acl_views_preference_page.png

Select which ACL group you want to set up by using the listing (2).

Then, for each view, you can define which specifi rights they have on it.

Warning

Whenever you change the configuration files on your Map 4 server you need to restart it afterwards (service tomcat6 restart)

Load / unload disabled resources

You can decide whether you want to load disabled resources into Map. If you do (which is the default configuration), all disabled resources will appear in the resource list. You will also be able to place them in your maps.

They will not have any status and will look like the following screenshot.

../../_images/disabled-resources.png

You can change this behavior by editing the /etc/centreon-studio/studio-config.properties file and adding the following line:

resource.load.enabled.only=true

Change herited status computation

You can decide whether or not you want downtimed and acknoledged elements to be taken into account in the computation of the herited status. By default, they are always taken into account. You can also choose to exclude from computation hosts and services whose severity is superior to a given value. By default, the value is very, very high.

To change that you need to edit your map 4 configuration file.

vim /etc/centreon-studio/studio-config.properties

Then add the following lines at the end of the file:

drilldown.useHardState = false
drilldown.ignoreElementInDowntime = true
drilldown.ignoreElementAcknowledged = true
drilldown.ignoreSeveritySuperior = 10

Now, if a service is CRITICAL but has been acknowledged, is in downtime or his severity is strictly superior to 10, the herited status of the host will be OK.

Highlight problems

You can change the size of elements based on their status to easily highlight problems. This only works when element are using the geometric style.

../../_images/guide_object_ratio_example.png

To do so, you need to modify the “Status size” properties in the Desktop’s preferences. Go to “Status > Status Size” to configure it globally or to “Views > Status > Status size” to configure it at view level.

../../_images/guide_ratio_preferences.png