Zsmith

Members
  • Content count

    6
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Zsmith

  • Rank
    Community Member
  1. I have been using a Powershell script for a while now that used Batch Script (to not use as much collector resources as my company has TONS of App Pools per box) This links Win32_PerfRawData_PerfProc_Process with Win32_Process using the process ID for discovery. Instead of having an ugly instance name (W3WP#1,W3WP#2 etc) it now will display the AppPool name from the command line. We recycle AppPools nightly. This will run discovery every hour as it stands although, the collection uses instance ID ,matching the Command line so no holes in the data LM Exchange ID: 2WHYY4
  2. This is how we do it. I will upload my datasource used to LM exchange if a similar one isn't already there
  3. Is there any plan to allow collectors to receive statd metrics? My current use case is for monitoring consul telemetry. Consul only exposes telemetry metrics via statsd/statsite streaming. I could create some wonky home brew parsing/ingestion with a script based datasource, but I'd rather not have such a large project to upkeep in my monitoring stack I've been using LM for over 2 years, made tons of custom datasources but not being able to stream metrics like this is the one thing that's been bothering me from the get-go. Currently I have this running on a Prometheus instance just for consul but I really want to keep my single pane of glass
  4. Any update on this one? I'd still like a way to post a graph link, or even a picture of the graph(like datadogs HipChat plugin)
  5. Has this been put on the roadmap or introduced yet? You can obviously do this via groovy or powershell custom datasources but a native feature would be great
  6. An important note that some coworkers of mine missed is you need to add the Fabric interconnects. Which is what the snap traffics through Attempting to add the management IP as my coworkers did leads to nothing being pulled We have 6 seperate pods now polling correctly, since we have HA FIs, each pod has 2 devices, the primary and secondary FI Hope this helps anyone else that isn't 100% familiar with UCS