Unlocking New Revenue & Control: Logs Partitions Arrive This October
Big news is on the horizon for MSPs. Starting in October 2025, LogicMonitor is rolling out Logs Partitions—a major upgrade that gives you the ability to isolate, meter, and control log data on a per-customer basis. This launch is designed to remove product limitations that have historically constrained MSPs, while opening the door to improved customer satisfaction, reduced cost to serve, and meaningful revenue growth. Speaking of big launches, keep your eyes open for the MSP Collective! This is a brand new community hub launching soon within the LM Community, designed exclusively for MSPs. It’s where you’ll be able to share strategies, join exclusive focus groups, and connect with peers who face the same opportunities and challenges you do. Top 5 Advantages of Logs Partitions for MSPs Here’s why Logs Partitions are a game-changer for managed service providers: New Revenue Streams with Flexible Packaging Transform logs from a cost center into a billable service. With retention-based tiers, you can package log analysis premium offerings for troubleshooting or compliance alongside infrastructure monitoring. Improved CSAT & Differentiated SLAs Deliver faster incident response and premium log reviews while offering audit-ready reporting that enhances customer trust. These value-added capabilities help you stand out in competitive markets and strengthen customer relationships. Visibility and Control Today, MSPs have visibility into log usage, but not control. Logs Partitions are here to change that. Built-in usage caps and shut-off thresholds empower you to manage consumption, prevent overruns, and deliver predictable costs for both you and your customers. Capture Larger Customers Partitioning at the customer level enables you to serve enterprise clients who demand strict data isolation, performance, and compliance guarantees - helping you compete for higher-value opportunities. Reduced Cost to Serve Logs Partitions help you serve more customers with fewer resources. AI-powered contextual analysis delivers 80% faster root cause analysis, freeing up 10-40% of engineering time. Logs Partitions aren’t just a technical upgrade - it provides new business models for MSPs. With the flexibility to reduce cost to serve while creating new revenue streams, you’ll be better positioned to grow profitably, increase customer satisfaction, and compete at the highest levels. Join the Webinar: From Cost to Competitive Edge Want to learn how to monetize Logs Partitions and package them into profitable services? Don’t miss our upcoming session: Webinar: From Cost to Competitive Edge – How MSPs Can Unlock Profit with LM Logs 📅 Date: Thursday, October 16, 2025 🕐 Time: 10:00 AM PT | 1:00 PM ET | 6:00 PM BST 🔗 Register here This session will cover packaging strategies, tiered pricing models, and practical ways to align LM Logs with customer outcomes. Stay tuned for more updates in the community as we count down to October, and be on the lookout for invitations to join the new MSP Collective!67Views2likes4CommentsObservability & Edwin AI steps
Hi fellow LM wizards, We want to elevate our monitoring as a big MSP. Did someone try to elevate to monitoring as code and create advanced observability? We are not aware what should be fixed or in place to follow the path to Edwin AI or advanced observability. Is there anyone who can share a roadmap with logical steps? Thank you in advance!38Views0likes0CommentsProvide a method for assigning group visibility independent of user roles.
We want to be able to show our clients their device groups in LM, but that currently requires making a new role for every client user due to group visibility only being able to be modified on the role rather than on the user directly. If we could assign visibility directly to users, that would allow us to control all non-group viewing permissions for clients from a single unified role due to them having otherwise identical perms. There may be other ways to implement a solution to address this such as group inheritance, but the only option that currently exists is to manage hundreds of nearly identical roles, each one attached to a single client user. Any general updates to customer permissions (stuff that isn't related to device viewing permissions) right now requires changing permissions in those hundreds of roles to match each other rather than adjusting a single permission on a single role.10Views1like6Commentsoption to require FQDN
As we have run into numerous cases now where the device name uniqueness requirement has bitten us, my recommendation to LM is now this: * add a portal option to require a FQDN for all devices -- failure to include would cause rejection * add an option to have a default FQDN suffix defined as a group property which would be used when adding a new device within that group I am not sure what to suggest for Websites and the new Services naming, but similar issues apply, especially for the current RBAC-based MSP model.3Views0likes0CommentsManaging Alert visibility on a "per-group" level
Good Morning all, we are a multi-Team managed service provider who, surprisingly, manages customers team-wise. We are in the process of switching to LogicMonitor right now and we have some issues regarding shared devices and their DataSource Instances, that belongs to different teams. We created Devicegroups for our teams, but if we put shared devices like loadbalancer, firewalls, storages etc. in said groups, ALL teams will see ALL alarms, regardless of responsibility. If one team decides to turn off an alarm on a shared device, the alarm is obviously deactivated on all other teams, as well. I'm aware of the Datasourceinstance grouping mechanism, but afaik it cant help with the problems i mentioned. We would like to request a feature where you can somehow mask datasources, their instances and their respective alarms based on the group you are in while you're viewing the device, so alarms and instances that don't belong to your team doesn't show up at all. It would be really convenient to somehow configure a "view" of a device based on the group you are in that doesn't interfere with the device datasources. Bonuspoints if you bring in alarm-tuning in this somehow. :)/emoticons/smile@2x.png 2x" title=":)" width="20"> Regards, Bastian10Views1like3Comments