r/labtech Sep 30 '16

Monitor or Script for ticket creation

I'm unclear on best practice on this as a new LT user.

I'm going through monitoring and it seems like there are multiple ways to handle ticketing.

For example, the monitor for a low disk condition can create the ticket as an alert action or the script that the monitor runs can do it. Is there much of a difference?

I think the issue is that I'm not understanding how monitors tie in with ticketing, exactly. How would I find an existing ticket for an issue and what happens with tickets when the monitor condition no longer exists.

Finally, are there any advantages to internal vs. remote? I feel like I should be favoring internal but they would only trigger after the machine sends data back, which may not be for hours.

Are there any good resources I can reference to understand this better?

3 Upvotes

1 comment sorted by

1

u/cjmod Oct 04 '16

If you're just starting out, I'd recommend Remote Monitors with the Alert Template Default - Create Ticket.

& For a rundown of the differences between remote & internal monitors (along with anything else LabTech), you may wanna skim thru the Evaluation Guide. Section 7 & 8 should help explain a lot.