LogicMonitor Community Guidelines
Welcome to the LogicMonitor Community! This space is dedicated to helping customers of all experience levels connect, collaborate, and grow their expertise with LogicMonitor. By participating here, you’re contributing to a stronger, smarter, and more supportive user ecosystem—and we’re thrilled to have you be part of it. These guidelines outline how to ensure our community remains a safe, valuable, and productive environment for everyone. 🎯 Our Community Purpose The LogicMonitor Community is here to help members: Exchange ideas and ask questions about the LM Envision platform and related topics Discover best practices from peers and LogicMonitor experts Engage with the Product team to learn what’s new and what’s next Build meaningful peer-to-peer relationships through helpful dialogue and shared experiences Contribute to a thriving ecosystem that supports the professional growth of all IT practitioners ✅ What’s Appropriate to Post Please use the Community to: Ask technical questions or platform how-tos Share your experience or creative LM use cases Recommend best practices or automation tips Discuss product features, roadmap feedback, or improvement ideas Find recaps of community events, webinars, or LogicMonitor programs Celebrate customer success stories and milestones ❌ Avoid posting: Irrelevant, off-topic, or repetitive content Personal or sensitive data (e.g., credentials, PII) Advertising, promotional, or third-party marketing material Trolling, harassment, or confrontational comments Explicit, graphic, or offensive material of any kind 💬 Engaging with Peers & Growing the Community We grow stronger through thoughtful participation and mutual support. Here’s how to keep the momentum going: Be kind and respectful. Assume positive intent and treat others how you’d like to be treated. Respond thoughtfully to posts—even if it’s just to say “Thanks!” or “This helped me too!” Tag others if you think they can help or have a relevant perspective. Share solutions or reference our Support Docs when applicable. 📢 Providing Feedback to Improve the Community Do you have an idea for how to improve the community? We’re listening! You can: Post your suggestions in the Community Feedback forum Tag a Community Manager in your post Email us at community@logicmonitor.com We love hearing from you! Many of our best features started with member feedback. 🚫 Violations & Escalation Path To ensure safety and respect for all members, we have a three-strike policy for handling inappropriate behavior: Strike 1 – Inform & Educate: You’ll receive a private warning explaining the guideline(s) violated and how to correct the behavior. Strike 2 – Final Warning: Continued issues will result in a second warning and temporary posting suspension. Strike 3 – Removal: Persistent or severe violations will lead to permanent removal from the community. Serious or one-time egregious behavior (e.g., hate speech, abuse, spam attacks) may result in immediate removal without warning at the discretion of the Community Team. 🙋 Need Help? If you have any questions about these guidelines or need support navigating the community: Visit the Community Welcome Hub Reach out to skydonnell or SuzanneShaw for guidance Email us directly at community@logicmonitor.com By following these guidelines, you help create a supportive, engaging, and insightful community for all LogicMonitor users. Thanks for being part of it!👋 Welcome to the LogicMonitor Community!
We’re excited to have you here! Whether you’re just starting out with LogicMonitor or have years of experience under your belt, you belong in this space. Our Community is your hub for connecting with other LM users, sharing insights, learning best practices, and gaining deeper value from your LogicMonitor experience. ❓Why Join? The LogicMonitor Community is where customers of all experience levels come together to: Engage with fellow users to solve challenges, exchange ideas, and learn from one another. Share and discover best practices for maximizing the potential of the LM Envision platform. Connect with our Product team to gain exclusive insight into what’s coming next on our roadmap and provide feedback that shapes the platform’s future. ⭐ What You’ll Find Inside Best Practices for Practitioners: A content series spotlighting ways to optimize monitoring, alerting, and performance across your environment. Voice of the Customer: Stories, feature highlights, and expert tips shared by real users. Events that Inspire: From virtual roundtables to in-person gatherings, our events are designed to foster collaboration, elevate your expertise, and help you grow as an IT professional. Look out for: Product Power Hours User Groups Exclusive previews of our upcoming MVP Program (launching Fall 2025) 🚀 Ready to Dive In? Here’s how to get started: ✅ Create your profile and introduce yourself in the Welcome forum. 💬 Join a discussion in our Product Forums or Feature Requests section. 📆 Sign up for an upcoming event to meet peers and LM experts. 🌟 Visit our program hubs to explore Product Power Hours, User Groups, or the MVP program. Whether you’re here to ask, answer, explore, or advocate, you’re in the right place. Let’s grow together. Welcome aboard, —The LogicMonitor Community Team
SQL Server Services monitoring for non-admin account
I am trying to add SQL Server Services (SQL Server Agent, SQL Server Browser) for non-admin accounts. For Collector server it is auto discovered because the service account is part of local admin group. I have trouble setting it up for non-admin account. (WinSQLServices module in Logic Monitor). I followed steps from documentation: https://www.logicmonitor.com/support/getting-started/advanced-logicmonitor-setup/windows-server-monitoring-and-principle-of-least-privilege#h-granting-windows-service-permissions-nbsp-sddl-nbsp-changes It didn't work. SDDL doesn't seem to be changing anything and after running active discovery SQL Server Services are not showing up for other servers with non-admin account. There is not much information about troubleshooting it. Are there specific SDDL string changes needed? Is there an order in which this string supposed to go? Are there specific permissions needed?
