User Profile

Patrick_Friar

LM Champion

Joined 7 years ago

6 Posts31 Likes1 Solution

Background in telecommunications, web development. Technical Support manager @ LogicMonitor supporting our product since 2018. Girl-dad. Amateur astronomer. Taco enthusiast.

View All Badges

User Widgets

Contributions

Re: Trial Account
Hey achurak I hope you're well! I wanted to let you know that I've reached out internally to our sales team to ensure that someone is reaching out to you about this request. Feel free to let me know here if you don't hear from somebody before the end of the week, thanks!
2 years ago Place Product Discussions
24Views
0likes
0Comments
Re: Does this frustrate anyone else?
@Mike Moniz the unique DS# is more useful internally than externally as it can be referenced in our backend logs when investigating issues with specific alerts, the associated LMD can be checked to verify during these searches as well as in alert frequency reporting, etc. While I don’t have any hard data on the design I would think that using LM-generated IDs in ticketing systems might lead to some very sporadic behavior and ultimately cause more of a headache, hence allowing the ticketing systems to follow their own ID schema.
2 years ago Place Product Discussions
97Views
7likes
0Comments
Re: CIENA MCP - API Datasource
Hey @DanT hope everything is going well! I’ll say, in my 5 years working with our customers I’ve not come across anything for CIENA MCP monitoring, we do have a suite for CIENA Waveserver. It may be worth submitting this request as Product Feedback to develop official support even if you do pursue this yourself, just remember to include your desired datapoints and any relevant API documentation for our developers to work from! You can submit feedback directly from your LogicMonitor portal by clicking Support > Contact Support > Feedback (the same place you’d open a ticket or chat with an engineer).
3 years ago Place Feature Requests
91Views
3likes
0Comments
Re: Introduce Yourself!
Howdy all, Patrick here, I am one of the US support managers. I’ve been with LogicMonitor for 4.5 years on the support team as an engineer/senior/lead and manager. Some of you may be familiar with me already! My background is in telecommunications (wire line and outside plant maintenance), web/api development (JS/Node/Angular), and SaaS support. I recently moved out of Texas and currently work out of the Eastern Panhandle of West Virginia with my wife, 8 year old, 2 cats, and father in law. @Joe Williams How has MTG been with your kiddo? I’ve recently gotten mine into Munchkin and have given serious consideration to digging out my old decks from their decade-old unpacked moving box. @Stuart Weenig I’ll be sure to bring the cards next time I come back down to ATX. Looking forward to it!
3 years ago Place Welcome
59Views
11likes
0Comments
Re: Any way to pull historical SDT report?
Hey Guru, in the portal SDTs are only indicated and included in Alert reporting while the SDT is still active. Mike and Stuart have given some excellent recommendations here where you may find historical SDT data via API, but if you’re interested in seeing such a report built-in to the product then I would recommend submitting Feedback to our product team directly to request this. You can find the option to submit Feedback within the support menu in your LogicMonitor portal along with the options to open a support ticket or chat- https://www.logicmonitor.com/support/about-logicmonitor/customer-support/get-support-resources#contacting
3 years ago Place Product Discussions
160Views
10likes
0Comments
Re: ParserError during PowerShell script execution - Bug or design?
Chiming in here to provide some public clarification as I've done some additional review of the issue and response that you've received from our support team- It seems that there was some unfortunate misunderstanding when first receiving your ticket. I did review the engineering plans that were referenced as the "incoming fix" and unfortunately they are unrelated to single or double-quote prematurely exiting strings and throwing parse errors. At this time there are no plans for this to be resolved through LM product changes. Our suggested workarounds are to use escape characters embedded within the property value itself which should prevent these issues from occurring, as we have seen similar problems with "$" used in properties/credentials in the past. As you noted in the ticket you can also get the data via API and sanitize it by stripping the single or double quotation, etc. when declaring your variables.
4 years ago Place Product Discussions
35Views
0likes
0Comments

Groups

Inner Circle
Welcome to the Customer Showcase, sponsored by “The Inner Circle “. Feel free to peruse this Customer Story Showcase to read more about what our customers are doing out in the world and how LogicMonitor is supporting their journeys.
12 Posts
Open Beta
Open Beta Process During this open beta period, we are asking that your team members flip the toggle and explore all the new features and functionality while attempting to complete their workflows in the new UI. Any identified bugs or feedback on critical functionality loss will help us to ensure your success and value in this new offering. *Please note, depending on what’s discovered, users can always toggle back to the current UI and continue with their work. Identified bugs or Feedback can be submitted through the following routes: Bugs: Please submit directly through the “Submit a Support Ticket” option using your instance. The more specific you can be on where you experienced the bug, the better. Functionality Feedback: Please submit through the “Feedback” option in your LogicMonitor instance and include “New UI” in the Subject line to ensure it’s routed appropriately.
72 Posts