You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the Monaco Service only applies monaco configuration for a configuration-change event that are triggered per service and per stage. This is great to ensure, e.g: metrics, SLOs or dashboards get created for a particular service or stage.
What is missing is the use case of applying project-wide configuration such as Tagging Rules, Project Management Zones, Naming Rules ...
I therefore suggest that the monaco service also handles sh.keptn.event.monitoring.configure and takes the monaco configuration on project level
The text was updated successfully, but these errors were encountered:
Right now the Monaco Service only applies monaco configuration for a configuration-change event that are triggered per service and per stage. This is great to ensure, e.g: metrics, SLOs or dashboards get created for a particular service or stage.
What is missing is the use case of applying project-wide configuration such as Tagging Rules, Project Management Zones, Naming Rules ...
I therefore suggest that the monaco service also handles
sh.keptn.event.monitoring.configure
and takes the monaco configuration on project levelThe text was updated successfully, but these errors were encountered: