Sonar Plugins

Add ability to configure metric thresholds

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: RADIATOR-1.1
  • Fix Version/s: RADIATOR-1.2
  • Component/s: Radiator
  • Labels:
    None
  • Number of attachments :
    0

Description

Example:
Current version: duplication is displayed in green for a 20% value like it is a good value but for sure it is not.
Next version: being able to configure thresholds. For example: max=0, min=20. For values greater than 20, display radiator boxes in red, between 0 and 20, use a color gradient from green to red.

Issue Links

is related to

Improvement - An improvement or enhancement to an existing feature or task. SONAR-3657 Treemap and Clouds : provide the ability to configure color range

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Freddy Mallet added a comment - - edited

Hi David, I guess it would be better to extend the Sonar platform in order to store this information in the metric table.

Show
Freddy Mallet added a comment - - edited Hi David, I guess it would be better to extend the Sonar platform in order to store this information in the metric table.
Hide
Permalink
David RACODON added a comment -

For sure, it would be the most logical way to achieve it.
Sonar could come with default values for each metric.
We'll still need a way to let the administrators configure these thresholds (something like for the SQALE remediation costs).

Show
David RACODON added a comment - For sure, it would be the most logical way to achieve it. Sonar could come with default values for each metric. We'll still need a way to let the administrators configure these thresholds (something like for the SQALE remediation costs).
Hide
Permalink
David RACODON added a comment -

Another idea:
Could we attach this configuration to a quality profile? Indeed, for example, for duplication, the expectations are not the same between Java and Cobol applications. Then, what about agregation with Views? Default values stored in the metric table would be used?

Show
David RACODON added a comment - Another idea: Could we attach this configuration to a quality profile? Indeed, for example, for duplication, the expectations are not the same between Java and Cobol applications. Then, what about agregation with Views? Default values stored in the metric table would be used?
Hide
Permalink
Freddy Mallet added a comment -

In fact that sounds good for me to reuse those alert settings attached to a quality profile (this could even be a way to cover SONARPLUGINS-1525).

Show
Freddy Mallet added a comment - In fact that sounds good for me to reuse those alert settings attached to a quality profile (this could even be a way to cover SONARPLUGINS-1525 ).
Hide
Permalink
David RACODON added a comment - - edited

I thought alerts could answer my need but after implementing the solution, I realized that they didn't.

Alerts are suitable for duplicated lines (%) : instead of having the worst value set at 100%, I can set it at 20% with an alert (error value = 20). Then I can reuse this threshold in the Radiator plugin.

Alerts are not suitable for comments (%) : instead of having the best value set at 100%, I'd like to have it set at 50%. I can't do it with an alert...

So I drew back to my first implementation: property at instance level : metric1:worst_value:best_value,metric2:worst_value:best_value,...

Do you have another idea?

Show
David RACODON added a comment - - edited I thought alerts could answer my need but after implementing the solution, I realized that they didn't. Alerts are suitable for duplicated lines (%) : instead of having the worst value set at 100%, I can set it at 20% with an alert (error value = 20). Then I can reuse this threshold in the Radiator plugin. Alerts are not suitable for comments (%) : instead of having the best value set at 100%, I'd like to have it set at 50%. I can't do it with an alert... So I drew back to my first implementation: property at instance level : metric1:worst_value:best_value,metric2:worst_value:best_value,... Do you have another idea?

People

  • Assignee:
    David RACODON
    Reporter:
    David RACODON
Vote (1)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: