discovery

3 Topics

Anybody else disabling Meraki instances by default?
If you are, I’d like to know if you’re experiencing the problem we are that LM has tried and failed to troubleshoot: For some random reason, a number of meraki instances disappear from LM during one discovery cycle and reappear during the next discovery cycle. This isn’t normally a big problem since they instances aren’t set to delete until 30 days. Normally, they’d just show back up and have a gap in data. However, in our casewe have a business need to have the instances disabled on discovery (we charge the customer per Meraki device we actively monitor). This means that instances that have been discovered and enabled for monitoring randomly disappear and reappear as disabled instances. Also, any customer instance level properties that were added to the instance also are not present on the rediscovered instance. In the last 3 hours, there have been 3,577 instances (out of somewhere around 18,000) that disappeared and reappeared in this way. The problem was so pervasive that I had to write a script to loop through all instances and enable them based on a master billing sheet.
Solved
Anonymous
2 years ago Place Product Discussions
300Views
14likes
11Comments
Automated DIscovery of Devices
Summary: We need to be able to automatically scan the network at regular intervals, searching for Switches/Firewalls/workstations/Laptops/Serversand report back someway (connectwise?/email report?) to what it finds and the changes. Details / Needs: To keep monitored systems in compliance (“matching”) with what we sold as MSP Be aware of new switches / servers / workstations on the network, and be able to up-sell based on new device counts
BAM
9 years ago Place Archive
2Views
0likes
1Comment
Automatic discovery of recipients/groups
We have begun implementing a tagging standard in our cloud accounts to better control discovered resources and route alerts accordingly. I would like to be able to route alerts by default based on the value of a tag. I'm aware that I can already set up specific users and then achieve exactly what I'm requesting, but I would much prefer to have a blanket rule that uses the tag's value as the recipient email address(es) directly. Some examples below: system.aws.tag.MonitorAlertEmail=ThisIsAnExample@PleaseOfferThisFeature.com system.aws.tag.SendAlertsHere=AnotherExcellentExample@WeWillPayExtraForThisFunctionality.gov AnotherEmailAddress@OkayNotReally.net See the screenshots below for a visual example of how I'd like to structure this automation.
Brandon
5 years ago Place Feature Requests
0Views
0likes
1Comment