Reference_metric parameter for PredictiveLevels?

Hi @moritz ,

why do we need to hardcode a “reference_metric” in the ruleset if we want to use PredictiveLevels?

This was not necessary in the past. The check_levels method got and still gets a metric_name and value.

I have a check plugin where the metric names are not predictable (pun intended).
How would I now implement the ruleset for that?

This is the old ruleset:

And this is the check plugin:

Within the application OTRS the admin is able to define their own ticket states. Therefor I cannot pre-define them in a ruleset.

Hi @r.sander !

We are planning one more DevHour where we could discuss all the DevAPI questions.
It is planned for 16th of July, at 3PM. I will announce it with more details beginning of the next week or so.
Maybe we could collect the questions and discuss them on the call if the time works for you?

Yes, that date works for me. Thanks for the suggestion.

1 Like

The call is scheduled :slight_smile: I have already added your 2 questions into the document.

1 Like

I have to remove the predicted level from the check plugin.