elastic / elastic/package-spec

Including SLO assets in Integrations.

Open
#435 19 comments 0 reactions 0 assignees View on GitHub
Team:Ecosystem
Dominant language
Go
Stars
20
Forks
93
Avg merge
15h 10m
Merged PRs (30d)
12

Description

The integration team has the technical know-how of supplying recommendations to the SLO systems. So, SLO configuration / recommendation can be shipped as an integration asset similar to dashboard assets.

Usage: When an integration is enabled, a set of recommendations for adding or updating SLOs appear to user.

**Advantage :**

a. Time saving for the user.

b. SLO metrics remain relevant when new metrics are introduced especially after a product upgrade

**SLO configuration UI have suggestions or recommendations?**

SLO configuration can also contain relationships to suggest recommendations.

Usecase : if cpu is considered, recommend to include memory. These dependency / recommendation mappings will be part of the SLO assets shipped with an integration

cc : @ruflin , @lalit-satapathy, @jsoriano

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.