2020-06-01 12:46:37 +02:00
|
|
|
package main
|
|
|
|
|
|
|
|
import (
|
|
|
|
"context"
|
|
|
|
"fmt"
|
|
|
|
"sort"
|
2021-05-15 12:25:57 +02:00
|
|
|
"strings"
|
2020-06-01 12:46:37 +02:00
|
|
|
"sync"
|
|
|
|
"time"
|
|
|
|
|
|
|
|
"github.com/VictoriaMetrics/VictoriaMetrics/app/vmalert/config"
|
|
|
|
"github.com/VictoriaMetrics/VictoriaMetrics/app/vmalert/datasource"
|
2022-02-02 13:11:41 +01:00
|
|
|
"github.com/VictoriaMetrics/VictoriaMetrics/app/vmalert/utils"
|
2020-06-01 12:46:37 +02:00
|
|
|
"github.com/VictoriaMetrics/VictoriaMetrics/lib/prompbmarshal"
|
|
|
|
)
|
|
|
|
|
|
|
|
// RecordingRule is a Rule that supposed
|
|
|
|
// to evaluate configured Expression and
|
|
|
|
// return TimeSeries as result.
|
|
|
|
type RecordingRule struct {
|
2021-02-01 14:02:44 +01:00
|
|
|
Type datasource.Type
|
2020-06-15 21:15:47 +02:00
|
|
|
RuleID uint64
|
2020-06-01 12:46:37 +02:00
|
|
|
Name string
|
|
|
|
Expr string
|
|
|
|
Labels map[string]string
|
|
|
|
GroupID uint64
|
|
|
|
|
2021-04-28 22:41:15 +02:00
|
|
|
q datasource.Querier
|
|
|
|
|
2020-06-01 12:46:37 +02:00
|
|
|
// guard status fields
|
|
|
|
mu sync.RWMutex
|
|
|
|
// stores last moment of time Exec was called
|
|
|
|
lastExecTime time.Time
|
2022-03-15 12:54:53 +01:00
|
|
|
// stores the duration of the last Exec call
|
|
|
|
lastExecDuration time.Duration
|
2020-06-01 12:46:37 +02:00
|
|
|
// stores last error that happened in Exec func
|
|
|
|
// resets on every successful Exec
|
|
|
|
// may be used as Health state
|
|
|
|
lastExecError error
|
2021-08-05 08:59:46 +02:00
|
|
|
// stores the number of samples returned during
|
|
|
|
// the last evaluation
|
|
|
|
lastExecSamples int
|
app/vmalert: extend metrics set exported by `vmalert` #573 (#654)
* app/vmalert: extend metrics set exported by `vmalert` #573
New metrics were added to improve observability:
+ vmalert_alerts_pending{alertname, group} - number of pending alerts per group
per alert;
+ vmalert_alerts_acitve{alertname, group} - number of active alerts per group
per alert;
+ vmalert_alerts_error{alertname, group} - is 1 if alertname ended up with error
during prev execution, is 0 if no errors happened;
+ vmalert_recording_rules_error{recording, group} - is 1 if recording rule
ended up with error during prev execution, is 0 if no errors happened;
* vmalert_iteration_total{group, file} - now contains group and file name labels.
This should improve control over specific groups;
* vmalert_iteration_duration_seconds{group, file} - now contains group and file name labels. This should improve control over specific groups;
Some collisions for alerts and recording rules are possible, because neither
group name nor alert/recording rule name are unique for compatibility reasons.
Commit contains list of TODOs for Unregistering metrics since groups and rules
are ephemeral and could be removed without application restart. In order to
unlock Unregistering feature corresponding PR was filed - https://github.com/VictoriaMetrics/metrics/pull/13
* app/vmalert: extend metrics set exported by `vmalert` #573
The changes are following:
* add an ID label to rules metrics, since `name` collisions within one group is
a common case - see the k8s example alerts;
* supports metrics unregistering on rule updates. Consider the case when one rule
was added or removed from the group, or the whole group was added or removed.
The change depends on https://github.com/VictoriaMetrics/metrics/pull/16
where race condition for Unregister method was fixed.
2020-08-09 08:41:29 +02:00
|
|
|
|
|
|
|
metrics *recordingRuleMetrics
|
|
|
|
}
|
|
|
|
|
|
|
|
type recordingRuleMetrics struct {
|
2022-02-02 13:11:41 +01:00
|
|
|
errors *utils.Gauge
|
|
|
|
samples *utils.Gauge
|
2020-06-01 12:46:37 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
// String implements Stringer interface
|
|
|
|
func (rr *RecordingRule) String() string {
|
|
|
|
return rr.Name
|
|
|
|
}
|
|
|
|
|
|
|
|
// ID returns unique Rule ID
|
|
|
|
// within the parent Group.
|
|
|
|
func (rr *RecordingRule) ID() uint64 {
|
2020-06-15 21:15:47 +02:00
|
|
|
return rr.RuleID
|
2020-06-01 12:46:37 +02:00
|
|
|
}
|
|
|
|
|
2021-04-28 22:41:15 +02:00
|
|
|
func newRecordingRule(qb datasource.QuerierBuilder, group *Group, cfg config.Rule) *RecordingRule {
|
app/vmalert: extend metrics set exported by `vmalert` #573 (#654)
* app/vmalert: extend metrics set exported by `vmalert` #573
New metrics were added to improve observability:
+ vmalert_alerts_pending{alertname, group} - number of pending alerts per group
per alert;
+ vmalert_alerts_acitve{alertname, group} - number of active alerts per group
per alert;
+ vmalert_alerts_error{alertname, group} - is 1 if alertname ended up with error
during prev execution, is 0 if no errors happened;
+ vmalert_recording_rules_error{recording, group} - is 1 if recording rule
ended up with error during prev execution, is 0 if no errors happened;
* vmalert_iteration_total{group, file} - now contains group and file name labels.
This should improve control over specific groups;
* vmalert_iteration_duration_seconds{group, file} - now contains group and file name labels. This should improve control over specific groups;
Some collisions for alerts and recording rules are possible, because neither
group name nor alert/recording rule name are unique for compatibility reasons.
Commit contains list of TODOs for Unregistering metrics since groups and rules
are ephemeral and could be removed without application restart. In order to
unlock Unregistering feature corresponding PR was filed - https://github.com/VictoriaMetrics/metrics/pull/13
* app/vmalert: extend metrics set exported by `vmalert` #573
The changes are following:
* add an ID label to rules metrics, since `name` collisions within one group is
a common case - see the k8s example alerts;
* supports metrics unregistering on rule updates. Consider the case when one rule
was added or removed from the group, or the whole group was added or removed.
The change depends on https://github.com/VictoriaMetrics/metrics/pull/16
where race condition for Unregister method was fixed.
2020-08-09 08:41:29 +02:00
|
|
|
rr := &RecordingRule{
|
2021-11-05 18:49:32 +01:00
|
|
|
Type: group.Type,
|
2020-06-15 21:15:47 +02:00
|
|
|
RuleID: cfg.ID,
|
2020-06-01 12:46:37 +02:00
|
|
|
Name: cfg.Record,
|
|
|
|
Expr: cfg.Expr,
|
|
|
|
Labels: cfg.Labels,
|
app/vmalert: extend metrics set exported by `vmalert` #573 (#654)
* app/vmalert: extend metrics set exported by `vmalert` #573
New metrics were added to improve observability:
+ vmalert_alerts_pending{alertname, group} - number of pending alerts per group
per alert;
+ vmalert_alerts_acitve{alertname, group} - number of active alerts per group
per alert;
+ vmalert_alerts_error{alertname, group} - is 1 if alertname ended up with error
during prev execution, is 0 if no errors happened;
+ vmalert_recording_rules_error{recording, group} - is 1 if recording rule
ended up with error during prev execution, is 0 if no errors happened;
* vmalert_iteration_total{group, file} - now contains group and file name labels.
This should improve control over specific groups;
* vmalert_iteration_duration_seconds{group, file} - now contains group and file name labels. This should improve control over specific groups;
Some collisions for alerts and recording rules are possible, because neither
group name nor alert/recording rule name are unique for compatibility reasons.
Commit contains list of TODOs for Unregistering metrics since groups and rules
are ephemeral and could be removed without application restart. In order to
unlock Unregistering feature corresponding PR was filed - https://github.com/VictoriaMetrics/metrics/pull/13
* app/vmalert: extend metrics set exported by `vmalert` #573
The changes are following:
* add an ID label to rules metrics, since `name` collisions within one group is
a common case - see the k8s example alerts;
* supports metrics unregistering on rule updates. Consider the case when one rule
was added or removed from the group, or the whole group was added or removed.
The change depends on https://github.com/VictoriaMetrics/metrics/pull/16
where race condition for Unregister method was fixed.
2020-08-09 08:41:29 +02:00
|
|
|
GroupID: group.ID(),
|
|
|
|
metrics: &recordingRuleMetrics{},
|
2021-04-30 08:46:03 +02:00
|
|
|
q: qb.BuildWithParams(datasource.QuerierParams{
|
2021-11-05 18:49:32 +01:00
|
|
|
DataSourceType: &group.Type,
|
2021-04-30 08:46:03 +02:00
|
|
|
EvaluationInterval: group.Interval,
|
2021-12-02 13:45:08 +01:00
|
|
|
QueryParams: group.Params,
|
2021-04-30 08:46:03 +02:00
|
|
|
}),
|
2020-06-01 12:46:37 +02:00
|
|
|
}
|
2021-02-01 14:02:44 +01:00
|
|
|
|
app/vmalert: extend metrics set exported by `vmalert` #573 (#654)
* app/vmalert: extend metrics set exported by `vmalert` #573
New metrics were added to improve observability:
+ vmalert_alerts_pending{alertname, group} - number of pending alerts per group
per alert;
+ vmalert_alerts_acitve{alertname, group} - number of active alerts per group
per alert;
+ vmalert_alerts_error{alertname, group} - is 1 if alertname ended up with error
during prev execution, is 0 if no errors happened;
+ vmalert_recording_rules_error{recording, group} - is 1 if recording rule
ended up with error during prev execution, is 0 if no errors happened;
* vmalert_iteration_total{group, file} - now contains group and file name labels.
This should improve control over specific groups;
* vmalert_iteration_duration_seconds{group, file} - now contains group and file name labels. This should improve control over specific groups;
Some collisions for alerts and recording rules are possible, because neither
group name nor alert/recording rule name are unique for compatibility reasons.
Commit contains list of TODOs for Unregistering metrics since groups and rules
are ephemeral and could be removed without application restart. In order to
unlock Unregistering feature corresponding PR was filed - https://github.com/VictoriaMetrics/metrics/pull/13
* app/vmalert: extend metrics set exported by `vmalert` #573
The changes are following:
* add an ID label to rules metrics, since `name` collisions within one group is
a common case - see the k8s example alerts;
* supports metrics unregistering on rule updates. Consider the case when one rule
was added or removed from the group, or the whole group was added or removed.
The change depends on https://github.com/VictoriaMetrics/metrics/pull/16
where race condition for Unregister method was fixed.
2020-08-09 08:41:29 +02:00
|
|
|
labels := fmt.Sprintf(`recording=%q, group=%q, id="%d"`, rr.Name, group.Name, rr.ID())
|
2022-02-02 13:11:41 +01:00
|
|
|
rr.metrics.errors = utils.GetOrCreateGauge(fmt.Sprintf(`vmalert_recording_rules_error{%s}`, labels),
|
app/vmalert: extend metrics set exported by `vmalert` #573 (#654)
* app/vmalert: extend metrics set exported by `vmalert` #573
New metrics were added to improve observability:
+ vmalert_alerts_pending{alertname, group} - number of pending alerts per group
per alert;
+ vmalert_alerts_acitve{alertname, group} - number of active alerts per group
per alert;
+ vmalert_alerts_error{alertname, group} - is 1 if alertname ended up with error
during prev execution, is 0 if no errors happened;
+ vmalert_recording_rules_error{recording, group} - is 1 if recording rule
ended up with error during prev execution, is 0 if no errors happened;
* vmalert_iteration_total{group, file} - now contains group and file name labels.
This should improve control over specific groups;
* vmalert_iteration_duration_seconds{group, file} - now contains group and file name labels. This should improve control over specific groups;
Some collisions for alerts and recording rules are possible, because neither
group name nor alert/recording rule name are unique for compatibility reasons.
Commit contains list of TODOs for Unregistering metrics since groups and rules
are ephemeral and could be removed without application restart. In order to
unlock Unregistering feature corresponding PR was filed - https://github.com/VictoriaMetrics/metrics/pull/13
* app/vmalert: extend metrics set exported by `vmalert` #573
The changes are following:
* add an ID label to rules metrics, since `name` collisions within one group is
a common case - see the k8s example alerts;
* supports metrics unregistering on rule updates. Consider the case when one rule
was added or removed from the group, or the whole group was added or removed.
The change depends on https://github.com/VictoriaMetrics/metrics/pull/16
where race condition for Unregister method was fixed.
2020-08-09 08:41:29 +02:00
|
|
|
func() float64 {
|
2021-08-05 08:59:46 +02:00
|
|
|
rr.mu.RLock()
|
|
|
|
defer rr.mu.RUnlock()
|
app/vmalert: extend metrics set exported by `vmalert` #573 (#654)
* app/vmalert: extend metrics set exported by `vmalert` #573
New metrics were added to improve observability:
+ vmalert_alerts_pending{alertname, group} - number of pending alerts per group
per alert;
+ vmalert_alerts_acitve{alertname, group} - number of active alerts per group
per alert;
+ vmalert_alerts_error{alertname, group} - is 1 if alertname ended up with error
during prev execution, is 0 if no errors happened;
+ vmalert_recording_rules_error{recording, group} - is 1 if recording rule
ended up with error during prev execution, is 0 if no errors happened;
* vmalert_iteration_total{group, file} - now contains group and file name labels.
This should improve control over specific groups;
* vmalert_iteration_duration_seconds{group, file} - now contains group and file name labels. This should improve control over specific groups;
Some collisions for alerts and recording rules are possible, because neither
group name nor alert/recording rule name are unique for compatibility reasons.
Commit contains list of TODOs for Unregistering metrics since groups and rules
are ephemeral and could be removed without application restart. In order to
unlock Unregistering feature corresponding PR was filed - https://github.com/VictoriaMetrics/metrics/pull/13
* app/vmalert: extend metrics set exported by `vmalert` #573
The changes are following:
* add an ID label to rules metrics, since `name` collisions within one group is
a common case - see the k8s example alerts;
* supports metrics unregistering on rule updates. Consider the case when one rule
was added or removed from the group, or the whole group was added or removed.
The change depends on https://github.com/VictoriaMetrics/metrics/pull/16
where race condition for Unregister method was fixed.
2020-08-09 08:41:29 +02:00
|
|
|
if rr.lastExecError == nil {
|
|
|
|
return 0
|
|
|
|
}
|
|
|
|
return 1
|
|
|
|
})
|
2022-02-02 13:11:41 +01:00
|
|
|
rr.metrics.samples = utils.GetOrCreateGauge(fmt.Sprintf(`vmalert_recording_rules_last_evaluation_samples{%s}`, labels),
|
2021-08-05 08:59:46 +02:00
|
|
|
func() float64 {
|
|
|
|
rr.mu.RLock()
|
|
|
|
defer rr.mu.RUnlock()
|
|
|
|
return float64(rr.lastExecSamples)
|
|
|
|
})
|
app/vmalert: extend metrics set exported by `vmalert` #573 (#654)
* app/vmalert: extend metrics set exported by `vmalert` #573
New metrics were added to improve observability:
+ vmalert_alerts_pending{alertname, group} - number of pending alerts per group
per alert;
+ vmalert_alerts_acitve{alertname, group} - number of active alerts per group
per alert;
+ vmalert_alerts_error{alertname, group} - is 1 if alertname ended up with error
during prev execution, is 0 if no errors happened;
+ vmalert_recording_rules_error{recording, group} - is 1 if recording rule
ended up with error during prev execution, is 0 if no errors happened;
* vmalert_iteration_total{group, file} - now contains group and file name labels.
This should improve control over specific groups;
* vmalert_iteration_duration_seconds{group, file} - now contains group and file name labels. This should improve control over specific groups;
Some collisions for alerts and recording rules are possible, because neither
group name nor alert/recording rule name are unique for compatibility reasons.
Commit contains list of TODOs for Unregistering metrics since groups and rules
are ephemeral and could be removed without application restart. In order to
unlock Unregistering feature corresponding PR was filed - https://github.com/VictoriaMetrics/metrics/pull/13
* app/vmalert: extend metrics set exported by `vmalert` #573
The changes are following:
* add an ID label to rules metrics, since `name` collisions within one group is
a common case - see the k8s example alerts;
* supports metrics unregistering on rule updates. Consider the case when one rule
was added or removed from the group, or the whole group was added or removed.
The change depends on https://github.com/VictoriaMetrics/metrics/pull/16
where race condition for Unregister method was fixed.
2020-08-09 08:41:29 +02:00
|
|
|
return rr
|
|
|
|
}
|
|
|
|
|
|
|
|
// Close unregisters rule metrics
|
|
|
|
func (rr *RecordingRule) Close() {
|
2022-02-02 13:11:41 +01:00
|
|
|
rr.metrics.errors.Unregister()
|
|
|
|
rr.metrics.samples.Unregister()
|
2020-06-01 12:46:37 +02:00
|
|
|
}
|
|
|
|
|
2021-06-09 11:20:38 +02:00
|
|
|
// ExecRange executes recording rule on the given time range similarly to Exec.
|
|
|
|
// It doesn't update internal states of the Rule and meant to be used just
|
|
|
|
// to get time series for backfilling.
|
|
|
|
func (rr *RecordingRule) ExecRange(ctx context.Context, start, end time.Time) ([]prompbmarshal.TimeSeries, error) {
|
|
|
|
series, err := rr.q.QueryRange(ctx, rr.Expr, start, end)
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
duplicates := make(map[string]struct{}, len(series))
|
|
|
|
var tss []prompbmarshal.TimeSeries
|
|
|
|
for _, s := range series {
|
|
|
|
ts := rr.toTimeSeries(s)
|
|
|
|
key := stringifyLabels(ts)
|
|
|
|
if _, ok := duplicates[key]; ok {
|
|
|
|
return nil, fmt.Errorf("original metric %v; resulting labels %q: %w", s.Labels, key, errDuplicate)
|
|
|
|
}
|
|
|
|
duplicates[key] = struct{}{}
|
|
|
|
tss = append(tss, ts)
|
2020-06-01 12:46:37 +02:00
|
|
|
}
|
2021-06-09 11:20:38 +02:00
|
|
|
return tss, nil
|
|
|
|
}
|
2020-06-01 12:46:37 +02:00
|
|
|
|
2021-06-09 11:20:38 +02:00
|
|
|
// Exec executes RecordingRule expression via the given Querier.
|
2022-03-29 15:09:07 +02:00
|
|
|
func (rr *RecordingRule) Exec(ctx context.Context, ts time.Time) ([]prompbmarshal.TimeSeries, error) {
|
|
|
|
qMetrics, err := rr.q.Query(ctx, rr.Expr, ts)
|
2020-06-01 12:46:37 +02:00
|
|
|
rr.mu.Lock()
|
|
|
|
defer rr.mu.Unlock()
|
|
|
|
|
2022-03-29 15:09:07 +02:00
|
|
|
rr.lastExecTime = ts
|
|
|
|
rr.lastExecDuration = time.Since(ts)
|
2020-06-01 12:46:37 +02:00
|
|
|
rr.lastExecError = err
|
2021-08-05 08:59:46 +02:00
|
|
|
rr.lastExecSamples = len(qMetrics)
|
2020-06-01 12:46:37 +02:00
|
|
|
if err != nil {
|
2020-06-30 21:58:18 +02:00
|
|
|
return nil, fmt.Errorf("failed to execute query %q: %w", rr.Expr, err)
|
2020-06-01 12:46:37 +02:00
|
|
|
}
|
|
|
|
|
2021-05-15 12:25:57 +02:00
|
|
|
duplicates := make(map[string]struct{}, len(qMetrics))
|
2020-06-01 12:46:37 +02:00
|
|
|
var tss []prompbmarshal.TimeSeries
|
|
|
|
for _, r := range qMetrics {
|
2021-06-09 11:20:38 +02:00
|
|
|
ts := rr.toTimeSeries(r)
|
2021-05-15 12:25:57 +02:00
|
|
|
key := stringifyLabels(ts)
|
|
|
|
if _, ok := duplicates[key]; ok {
|
2020-06-01 12:46:37 +02:00
|
|
|
rr.lastExecError = errDuplicate
|
2021-05-15 12:25:57 +02:00
|
|
|
return nil, fmt.Errorf("original metric %v; resulting labels %q: %w", r, key, errDuplicate)
|
2020-06-01 12:46:37 +02:00
|
|
|
}
|
2021-05-15 12:25:57 +02:00
|
|
|
duplicates[key] = struct{}{}
|
2020-06-01 12:46:37 +02:00
|
|
|
tss = append(tss, ts)
|
|
|
|
}
|
|
|
|
return tss, nil
|
|
|
|
}
|
|
|
|
|
2021-05-15 12:25:57 +02:00
|
|
|
func stringifyLabels(ts prompbmarshal.TimeSeries) string {
|
2020-06-01 12:46:37 +02:00
|
|
|
labels := ts.Labels
|
2021-05-15 12:25:57 +02:00
|
|
|
if len(labels) > 1 {
|
|
|
|
sort.Slice(labels, func(i, j int) bool {
|
|
|
|
return labels[i].Name < labels[j].Name
|
|
|
|
})
|
|
|
|
}
|
|
|
|
b := strings.Builder{}
|
|
|
|
for i, l := range labels {
|
|
|
|
b.WriteString(l.Name)
|
|
|
|
b.WriteString("=")
|
|
|
|
b.WriteString(l.Value)
|
|
|
|
if i != len(labels)-1 {
|
|
|
|
b.WriteString(",")
|
|
|
|
}
|
2020-06-01 12:46:37 +02:00
|
|
|
}
|
2021-05-15 12:25:57 +02:00
|
|
|
return b.String()
|
2020-06-01 12:46:37 +02:00
|
|
|
}
|
|
|
|
|
2021-06-09 11:20:38 +02:00
|
|
|
func (rr *RecordingRule) toTimeSeries(m datasource.Metric) prompbmarshal.TimeSeries {
|
2020-06-01 12:46:37 +02:00
|
|
|
labels := make(map[string]string)
|
|
|
|
for _, l := range m.Labels {
|
|
|
|
labels[l.Name] = l.Value
|
|
|
|
}
|
|
|
|
labels["__name__"] = rr.Name
|
|
|
|
// override existing labels with configured ones
|
|
|
|
for k, v := range rr.Labels {
|
|
|
|
labels[k] = v
|
|
|
|
}
|
2021-06-09 11:20:38 +02:00
|
|
|
return newTimeSeries(m.Values, m.Timestamps, labels)
|
2020-06-01 12:46:37 +02:00
|
|
|
}
|
|
|
|
|
2020-06-01 13:34:58 +02:00
|
|
|
// UpdateWith copies all significant fields.
|
2020-06-01 12:46:37 +02:00
|
|
|
func (rr *RecordingRule) UpdateWith(r Rule) error {
|
|
|
|
nr, ok := r.(*RecordingRule)
|
|
|
|
if !ok {
|
|
|
|
return fmt.Errorf("BUG: attempt to update recroding rule with wrong type %#v", r)
|
|
|
|
}
|
|
|
|
rr.Expr = nr.Expr
|
|
|
|
rr.Labels = nr.Labels
|
2021-05-22 23:26:01 +02:00
|
|
|
rr.q = nr.q
|
2020-06-01 12:46:37 +02:00
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
2022-03-15 12:54:53 +01:00
|
|
|
// ToAPI returns Rule's representation in form
|
|
|
|
// of APIRule
|
|
|
|
func (rr *RecordingRule) ToAPI() APIRule {
|
|
|
|
r := APIRule{
|
|
|
|
Type: "recording",
|
|
|
|
DatasourceType: rr.Type.String(),
|
|
|
|
Name: rr.Name,
|
|
|
|
Query: rr.Expr,
|
|
|
|
Labels: rr.Labels,
|
|
|
|
LastEvaluation: rr.lastExecTime,
|
|
|
|
EvaluationTime: rr.lastExecDuration.Seconds(),
|
|
|
|
Health: "ok",
|
|
|
|
LastSamples: rr.lastExecSamples,
|
2020-06-01 12:46:37 +02:00
|
|
|
// encode as strings to avoid rounding
|
2022-03-15 12:54:53 +01:00
|
|
|
ID: fmt.Sprintf("%d", rr.ID()),
|
|
|
|
GroupID: fmt.Sprintf("%d", rr.GroupID),
|
|
|
|
}
|
|
|
|
|
|
|
|
if rr.lastExecError != nil {
|
|
|
|
r.LastError = rr.lastExecError.Error()
|
|
|
|
r.Health = "err"
|
2020-06-01 12:46:37 +02:00
|
|
|
}
|
2022-03-15 12:54:53 +01:00
|
|
|
return r
|
2020-06-01 12:46:37 +02:00
|
|
|
}
|