Todd Theoret

Members
  • Content Count

    26
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Todd Theoret

  • Rank
    Observer

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Stuart....I wanted to thank you again for your guidance....and patience... with this manual mapping. I was able to get the functionality to work on a small scale. Thank you!
  2. What would the TS code be which generated the output above?......please.
  3. We are staring at the fishline Stuart. Hopefully last question and an example: 1. (example): write a TopologySource that ties those ERIs together: Any chance you could provide the TS configurations utilized to actually build the dependencies? Thank you again Stuart.
  4. Getting closer...any chance you could provide an example of what the configs for the custom device ERI PropertySources would look like? Thank you again. [Ping/Host Status Only] 1. Device1: 10.1.1.1 (RCA – Entry Point] a. ERI PropertySource Example 2. Device2: 10.1.1.2 [child to Device1] a. ERI PropertySource Example 3. Device3: 10.1.1.3 [child to Device1] a. ERI PropertySource Example
  5. Still not clear Stuart.... 1. Are the "instances" actually other device displayNames being monitored? 2. Is the datasource applied to just a single device?....possibly the device utilized as a "Entry-Point for Topology Based Dependency"? 3. Do you have an example of a "Root Cause Analysis" entry based on this manual topology configurations to support the alerting suppression for downstream devices? Thank you for your time!
  6. Just asking incase someone is in a great mood today ....any chance someone could provide a sample or two of a couple devices and the associated new custom properties which are required? Are the below property names accurate...or close? What values are required for the properties? topo.namespace topo.blacklist edge_type from_obj to_obj edges An example or two would really assist...and would be so much appreciated!
  7. Stuart...when trying to register for the zoom call....today is not an option you can select.
  8. Thank you for replying!...any chance you have a sample of this Manual_Topology script populated to show the required hardcoded syntax and format? I believe I found the module you are referencing:
  9. You think we can do it! What would it take to have a call with you to discuss further? We are an MSP and need this capability ...."yesterday :)" to decrease the number of tickets created by dependent devices. Just for reference: I am familiar with the TopologySources/Mapping/Root Cause Analysis....pretty slick. I even circled back and retested...again...using these two datasets. Neat concept but not a solution for our requirements.
  10. Thank you Stuart. Any chance there is a potential solution being developed which would allow....manually tagging....devices?
  11. Just following up to see what progress has been made and possible ETA for a solution to manage the "Parent/Child Relationships Alerting Suppression"....for use on all devices being monitored....and not using the Mapping option. Please advise. Thank you!
  12. Has LogicMonitor made any adjustments to support how Meraki sends NetFlow traffic?
  13. Tom, I just started taking advantage of PropertySources. I haven't solved the switch stack (models, sn#'s and firmware) yet. I came across this post. Any chance you got the Cisco-IOS working yet? Thanks as always Tom.
  14. Is it possible to pull a devices' auto.properties through the REST API?
  15. Thank you Tom (as always) Also, just fyi....I came across another post [Using PropertySources for Reporting] by Billy Yuliadi, which presented an additional option. I just shared the PropertySource M44C23. Thank you Billy!