Recent Content
Use Policy Usage
Hi all! We're looking at some improvements in user policy management, and as we do this we'd like to understand more about how you all are using it. So, a few questions: Are you using user policies for local accounts to manage the password fields (Password Strength, Password Expiration, Password Shadowing, Password Reset) through a user policy? Are you using user policies to switch local accounts to ldap/ad accounts through the user policy using the authentication method field? Are you using the default user policies or are you using custom policies? thanks in advance!Join ScienceLogic VP of Solutions and Ecosystems Douglas James at NexusLive Oct 7-9th
Join ScienceLogic VP of Solutions and Ecosystems Douglas James as he moderates our Customer Panel at hashtag#NexusLive2025! In this interactive panel, customers will share how they advanced their operations by aligning ScienceLogic with real business needs. Learn how they built early wins, reduced noise, and scaled automation and AI to unlock lasting value. 🔗 Register for hashtag#NexusLive2025 today: https://bit.ly/4motupI 🗓️ October 7-9 | Reston, VA
Config push process Vs Appliance page config push force
Could you help me understand the background processes when I initiate a "Force Config Push" (e.g., by clicking the lightning bolt icon) vs what differs from the standard config push process?' What steps does the system execute during a "Force Config Push" to apply configuration changes to managed devices? If the configuration push process is disabled, will clicking "Force Config Push" still result in a complete and successful configuration update to the target device(s)? Thanks
putting a 2 node SL1 HA database env in maintenance
I have 2 databases in an HA setup I see Enable Cluster Maintenance as one of the choices in coro_config can I select this on both database and be able to do VMWare snapshots before doing upgrades and the databases will be in a "non writable state?"Unnecessary API calls in Meraki API v115
Hello everyone, We are removing the Meraki API v115 PowerPack from the product download portal as we have discovered it shipped with code that requests the "/api/v1/networks/<dependency>/topology/linkLayer" endpoint even though the collection objects that utilize that data have not been added to the PowerPack yet. This was intended to be shipped "dark" so it could be flipped on easily in the future when topology mapping features in the platform are available to take advantage of the data. However, since they are enabled in v115, users with a large number of networks in Meraki may experience unnecessary API calls (1 call per network every 5 minutes) being made which can cause API rate limit issues and/or additional collector load that previously was not there. This behavior would be expected in the future should a user "opt-in" to this additional API overhead in order to collect and utilize this topology data, but as there is no functionality currently available to utilize this data once retrieved, it's simply extra work for the collector and API. We are publishing a KB article soon to explain how to disable this (change "true" to "false" in the request manager snippet where this API call is listed.) and we will be releasing Meraki API v115.1 in the next few weeks. We apologize for any inconvenience. - Taylor
