Monitoring system ticket workflow

[Steven Miller]

I am looking to setup out monitoring system (PRTG) to send emails into JSM when it detects issues. As configured, the system also send an email automatically when the issue is resolved. Ideally the 'resolved' email will trigger the initial request to close out.

So I have a few questions:

Is anyone here using JSM with a monitoring system in this way?

Assuming the initial issue ticket and the resolved ticket will send separately, how can this be reconciled in JSM to prevent multiple tickets opening? 

My goal as stated is so that any alert will open a ticket to be investigated, and also any issues that is resolved (or goes away on its own) will trigger the automatic closure of the ticket,

[mararn1618 _secretbakery.io_]

Hi @Steven Miller,

I belive the easiest way to achieve this is via REST API and not Email. Example:

• Create a ticket via REST API ( link to api )
• To remember the reference to that ticket you can
  • (a) Remember in JIRA: Include a reference known to your monitoring sytem in the ticket summary or custom field (e.g. PRTG-ID-1234)
  • (b) Remember in PRTG: Remember the key of the created issue
• Once the issue is resolved, update that ticket
  • (a) Find the ticket via ( link to api ) and update it via link to api
  • (b) In case you remember the Issue key in PRTG, just update via link to api

If you want to do that via email, my thoguhts are:

• Set up tickets & comments via email https://support.atlassian.com/jira-cloud-administration/docs/create-issues-and-comments-from-email/
• Create the ticket via email
• Remember the ticket id from the reply (reply email subject), e.g. ISSUE-123
• When the ticket is resolved send yet another email, using the ticket id ISSUE-123 in the subject. This will add the new email as a comment.
• Create an automation that will close the ticket based on the comment

Cheers, Markus
Founder of Duplicate AI, Find & Merge Similar Issues

[Jay Jones]

Hi Mararn1618_secretbakery_io_,

I am interested in a ticketing system for customer inquiries, with solid APIs that can help us maximize our customer service and work flow. My company is Data Abstract Solutions, Inc. Currently way use Outlook email which connects with eWayCRM. My associates are having to correspond through the entire process using email.

We also use Jira 8.1 if that helps.

We have 10 or so main clients and want them to be able to login and submit a ticket with all the appropriate information on the form: Name, company, title, email, phone, current date, issues, county, state, etc.

My name is Jay and I am the Director of Operations for an Information Technology and Services company.

Let's discuss.

Jay Jones

jayj@dataabstractsolutions.com 

[Nic Brough -Adaptavist-]

Yes, I've been doing that sort of thing with Jira for years, by

• using apps that enable monitoring systems to easily talk to Jira, either apps for Jira or for the monitoring system
• with direct interfaces (the monitoring system uses SOAP or REST to push data into Jira)
• with pull scripts (things run in Jira and ask the monitoring system questions - not the best way to do this sort of thing)
• more recently, with Opsgenie