How to submit a Feature Request.
At LogicMonitor, we are dedicated to providing our customers with the best monitoring solutions and services. To ensure that we are meeting your needs, please share your feedback on our products by visiting our feedback form in the LM portal https://lmcloud.logicmonitor.com/santaba/uiv3/dashboard
To submit your feedback successfully, please follow these steps:
-
Click on the link provided
-
Sign in to your LogicMonitor account
-
Navigate to the ‘Support’ section
-
Click ‘Contact Support’
-
Lastly, click ‘Feedback’
-
Provide a summary and descriptive message
-
Click on ‘Submit’
Your input is invaluable in helping us understand how we can improve and continue to provide the best possible monitoring experience for our customers. You can share your ideas, vote on existing suggestions, and see what other members of our community are saying.
We appreciate your time and effort in providing feedback and look forward to hearing from you.
Thank you,
The LogicMonitor Community Team.
Thorwald
·1 year agoWhatever happened to the Feedback link that was in the portal (UIv3)?
You could simply ask a question, or provide feedback or submit a feature request.
Where the heck is the feedback/feature request option now?
@David Bond @Cole McDonald @Stuart Weenig as we are working through the process of Product engagement, Ideas and PB, please do not hesitate to tag me, or flag anything that needs immediate attention.
I may not know all the technical detail to respond, but I am happy work to get you answers!
Cole McDonald
·2 years agoThat depends on what your definition of “regularly” is.
I’m on a NOC team I check our whole communications platform every half an hour if I haven’t seen any notifications pop up on my screen, but that’s a realtime monitoring cadence … product management should have a daily expectation to get caught up. They should distribute/adjust the filtered info as needed for their teams to succeed in fulfilling the client needs. Not everything needs to jumped on in this situation obviously… but barring my reasonable expectation for consumption, communicating that the message was received at all would be 100% better than the current state.
LM User
·2 years agoThat depends on what your definition of “regularly” is.
Cole McDonald
·2 years agoIntegration between Community & Product Board is on the roadmap for later this year. We have a few technical constraints we need to work through, but we definitely hear you and once we get going we’ll have a feedback group here on Community.
My assumption was that the product teams were supposed to be checking here regularly. I’ve been both submitting feature requests and posting here in most cases. Mostly to help drive some visibility for the types of things we’re asking for. But I also use our account managers if we have info that has to stay internal. I made a mockup of a dashboard workflow for submission that included enough client info that our policy required it could only be delivered using an encrypted email… not PII, but contractual obligations. Based on some of my experience, I don’t expect to hear back on it unless it magically appears in a UI/UX session or the product itself.
David Bond
·2 years agoExcellent! Far better to have Feature Request discussions in the open, so we can all discuss / vote / contribute.
Integration between Community & Product Board is on the roadmap for later this year. We have a few technical constraints we need to work through, but we definitely hear you and once we get going we’ll have a feedback group here on Community.
hvittal
·3 years ago[ZBXNEXT-5878] Enhance permission checking/handling - ZABBIX SUPPORT
Above is an open source vendor taking feature requests… publicly sharing what requests have come in, voting by customers so you know it’s important to the user base.
They are sharing code changes, etc. which is TMI and not required but the concept is the best I have seen and it’s adopted by other enterprise vendors and keeps this open and honest about interests of the wider customer base.
Just a JIRA project with some minor customization and you can have something like above going and it’d improve the feedback experience tremendously IMHO.
LM User
·3 years agoWe need a Feature Request Revolution! ✊
I see that as the main reason to have switched community platforms.
Mark_Hensler
·3 years agoWe need a Feature Request Revolution! ✊
michaeld
·3 years agoLove @mnagel’s suggestion on having feature requests in the forums so users can provide feedback, further improvement ideas, etc. By giving customers a way to upvote requests from other customers you’ll be able to see where the common pain points are and where development focus should be.
Michael Dieter
·3 years agoIn general, I’d probably say that “Feedback” and “Feature Request” communication channels should get separated. An acceptable option would be providing a choice at Feedback creation:
“What is this feedback about?
In both cases, as a customer I very much want to be able to track the progress of any feedback or feature request that I might make and as noted above the current mechanism does not provide this; in fact b/c I don’t even get an ack or receipt I am pretty sure that I’ve submitted the same feedback multiple times.
So here’s hoping that the Feature Request pipeline (and the Feedback one too) is getting a makeover as part of this Community re-launch.
LM User
·3 years agoAgreed it’s been a black hole in the past. Interested to see what changes are in store now that the new community is going live, and Product Board is supposed to be in use. The general opinion of most LM customers about feature requests is stated pretty well above by @mnagel. It’s a one-way black hole. We submit through the product and never see anything about it ever again. Posting to the community has been good to get qualification of the request, but in the last 10 years, posts in the feature requests category have gotten next to 0 attention from LM.
LM: Listen to your existing customers, not just the fish that’s not yet on the hook. Your existing customers are where your ARR comes from.
mnagel
·3 years agoSorry, but the feedback mechanism is a one-way blackhole, at least from this side. Hiding feature requests behind feedback rather than being able to discuss them within the forum is not going to work. A better way to handle feature requests is to enable voting and perhaps use an assigned upvote count to each person as at least some other feature request systems work (e.g., you get N votes to assign to features, you can vote more than once and you can move them around). This change is a step in the wrong direction.