Skip to content
This repository has been archived by the owner on Apr 29, 2020. It is now read-only.

Tuning of monitoring/alerting #31

Closed
ghost opened this issue Feb 4, 2017 · 2 comments
Closed

Tuning of monitoring/alerting #31

ghost opened this issue Feb 4, 2017 · 2 comments

Comments

@ghost
Copy link

ghost commented Feb 4, 2017

We don't have good knowledge yet of how the metrics look like when actually using Jenkins. This issue has been split off #2, to continuously tune monitoring and alerting during the rest of the sprint (and beyond).
@ghost ghost mentioned this issue Feb 4, 2017
Closed
7 tasks
@ghost ghost added ready sprint labels Feb 4, 2017
@ghost ghost added this to the Sprint: CI/CD/Testing Infra/Automation milestone Feb 4, 2017
@victorb victorb mentioned this issue Feb 10, 2017
Closed
7 tasks
@Kubuxu Kubuxu removed the ready label Mar 2, 2017
@victorb victorb removed the sprint label Oct 6, 2017
@victorb victorb mentioned this issue Aug 13, 2018
Closed
@victorb
Copy link
Collaborator

victorb commented Aug 13, 2018

This issue was moved to ipfs-inactive/dev-team-enablement#81

@victorb victorb closed this as completed Aug 13, 2018
@victorb victorb mentioned this issue Aug 13, 2018
Open
@victorb
Copy link
Collaborator

victorb commented Aug 13, 2018

This issue was moved to ipfs-inactive/dev-team-enablement#82

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@victorb @Kubuxu