[
https://ovirt-jira.atlassian.net/browse/OVIRT-2503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38072#comment-38072
]
Dafna Ron commented on OVIRT-2503:
----------------------------------
[[email protected]] yes. but to remind you, when we discussed monitoring you
stated that we need to reply to every alert that comes in so that we know
nothing has been missed and I have also been looking into the best way to do
that (since I do not think that its viable in email).
I was discussing this issue with leads of some of the jboss developing team who
have been working agile for a while and they have recommended that we stop
doing monitoring in email and just configure a jira project for the monitoring
which would allow us to easily monitor every alert and assign them forward when
needed.
Jira is very flexible and we can configure it to do a lot of things that we
cannot do now.
I was also concerned about having too many opened tickets but then, if you have
a way to close/dismiss tickets quickly (which is something that is possible in
Jira) then I see it as two birds one stone since we would be able to:
1. make sure all alerts have been viewed by someone in the team.
2. give us an easier way to move forwards in collaboration with Dev on
monitoring and perhaps, partially automating it.
> Testing automatic Jira ticket logging for CQ monitoring
> -------------------------------------------------------
>
> Key: OVIRT-2503
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2503
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Reporter: Dafna Ron
> Assignee: infra
>
> As part of monitoring improvement and shifting partial responsibility for CQ
> monitoring to the developers I would like to do some experiments on
> connecting CQ alerts to create Jira tickets automatically.
> As we have the ost monitoring project we start by doing some tests on that
> project so that we do not overflow our jira with alerts.
> For now I would like to start with Jira's opening with the following
> specifications:
> 1. Subject: [ CQ ] [$patch number] [ oVirt $VER ($project) ] [ TEST NAME ]
> 2. at the beginning, email sent to: [email protected]
> 3. jira description [cq message]
> 4. all jira's has to have label=ost_failure and infra-owner as default.
> I would like to change the project type to allow:
> 1. easy closing of Jira's (one/two clicks if we can)
> 2. view of Jira's like service tickets (rather then bugs)
> There is a plugin called zapier that allows to easily connect a jira from an
> email and also allow to add some rules to the Jira which may make this easier
> for us.
> can you also install it and link it to the ost jira? I have an email account
> that we can use for that.
> [email protected]
> https://zapier.com/apps/jira/integrations
> [[email protected]]
> once I do some tests on my own on this, I wanted to try and collaborate with
> one of the projects (maybe networking or one of sandro's teams) where CQ
> failures would automatically open a ticket to their team and they can handle
> the monitoring and escalate issues to us if needed.
> Any advice on configurations we should be thinking of for that?
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100092)
_______________________________________________
Infra mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/[email protected]/message/2VG56TGACNFHAWGOKAYYQAJOUOPDRQK5/
