Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

Table of Contents


Alerts are simple boolean thresholds that will be applied to every project analyzed with the profile. To manage your alerts configuration, got to the profile's Alerts tab: 

From there, it is possible to fully manage alerts, by adding new ones, editing or deleting existing ones. To create a new alert you must choose:

  • the metric you are interested in
  • whether the alert will be checked against the current value of the measure or the variation of this measure
  • an operator (is greater than, is less than, etc.)

You will also need to specify at least one of:

  • the value that will trigger a warning
  • the value that will trigger an error

Alert changes will be applied during the next analysis. When a project crosses an alert threshold in either direction (either to raise an alert or to lay one to rest) an alert event is recorded on the project.

Metrics that have crossed an alert threshold will be highlighted in filters and on dashboards with gold or red, depending on whether they're at the warning or error stage:

Projects with active alerts will also be marked in filters with a yellow alert icon, as shown at left, above.

A summary of active alerts is available in the Alerts widget:


Alerts are not inherited from parent profiles.

Assigning a Project to a Quality Profile

To assign / unassign projects to / from a quality profile, go to the Projects tab:

When a project is not explicitly associated with a quality profile and there is no sonar.profile analysis property, the default quality profile of the relevant language is used to perform the next analysis. Project profile assignments may also be made from the project administration interface.

Profile Inheritance

Maintaining lots of quality profiles over time can be tedious. To ease this maintenance, the rule configuration of a quality profile can be inherited. For each profile, you can decide whether or not it has a parent profile on the Profile Inheritance tab:

This means that the quality profile inherits all the coding rules defined in the parent profile. Rule inheritance is indicated on the Coding rules tab by a small blue marker next to the coding rule:


A rule inherited from a parent cannot be deactivated. But it is possible to change its parameter(s) and/or its severity. If one of these values is changed, a red marker replaces the blue marker:

Changes made to an inherited coding rule can be reverted by clicking on the Revert to parent definition button:


Note that setting a parent profile will appear in a change log as the addition of that profile's rules to this one.



  • No labels