The Other Josh

Members
  • Content Count

    16
  • Joined

  • Last visited

  • Days Won

    2

Community Reputation

4 Neutral

About The Other Josh

  • Rank
    Observer

Recent Profile Visitors

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

  1. Is anyone using or planning on using CredentialGuard? We enabled it in the spring and ran into problems if the WMI user (via properties) wasn't the same as the service account. After a lot of work with support to identify the source of the problem, the final response was that it's an unsupported configuration. "This doesn't mean you cannot use Credential Guard, simply that it hasn't been officially tested and verified and any performance related issues cannot be remedied via support -- per the support team" The specific use of different accounts wasn't an issue for us; it was a leg
  2. I figured things out after contact with support; I got twisted because it appeared that we lost a stack port but it wasn't alerting. It turns out that it was never up, but that put me on the wrong track
  3. The filter option can't be only on device discovery, but filter on instance discover (ie it would stop adding an instance, but it would not be used to remove an existing instance).
  4. We also implemented the alarm for the SNMP uptime datasources, which covers situations where SNMP is misconfigured on not working. It will miss batchscript, script, WMI, etc so it's definitely not comprehensive. The problem with "No Data", and I've had some back-and-forth with the CSM, is that there is currently no way to tell if the "No Data" is intentional (if the datapoint is not relevant given the current status) or cause for a problem (data should be returned or is not). This shows up in scripts where they will set a datapoint in some paths but not others. The new SNMP inte
  5. I ran into this again, and I think that the current implementation is lacking. The problem is that there are many types of instances that can be 'down' in normal operation, but you want to alarm if they were up and now are down. However, if they are down when you add the device, you don't want to add the instance and have to manually delete them. Several examples: Unused redundant power supply Unused stack port Unused interface The current configuration leads to errors; I had support tell me to switch to 'save for 30 days' to get alarms for deleted
  6. I had some feedback about that one too. Doubling your interface count should have a bit more visibility. I was also pretty unhappy that the patch notes described it as "an identical replacement"; I like the direction but it's definitely still a WIP. The new collector sizes (XL and XXL) don't have any changes to the default batchscript threads. I opened a ticket on that and made some adjustments to the threadcount and didn't see any problem with other performance metrics.
  7. Good point, I do now recall frequently seeing hostProps. Setting it at the device level does result in a failure.
  8. Just the instance - I wanted to isolate the test.
  9. I was setting the creds on the instance that I was testing. Are you sure that the datasources you were testing were using the groovy API? I'll test caching later; right now still focused on the actual problem (this is just a side effect :). Yeah that link is handy. What is the convention that it breaks (I was looking at some other session options that might let you set authentication parameters) - assuming that you are checking for and only using it if wmi creds exist?
  10. Tested by setting wmi.user to 'thiswillnotwork' and both PollNow and collections are still working.
  11. I'm pretty sure that it doesn't do anything automatically with the properties. The issue we are working on is related to access rights on the service account vs the WMI account, which is why I wanted to do some testing while specifying different accounts. The WinCPU datasource is not working (it doesn't reference the properties) but other WMI data collection is fine. I am working with support but was checking here in parallel in case someone had the information readily available.
  12. Is there any documentation for the Groovy WMI implementation (com.santaba.agent.groovyapi.win32.WMI and com.santaba.agent.groovyapi.win32.WMISession)? I wasn't able to find anything in a short search. In particular, none of the examples that I found in LM check for WMI credential properties (wmi.user and wmi.pass).
  13. I keep waffling on whether this is a bug, feature request or I'm just thinking about it wrong. Currently, if you configure instances to delete automatically it will prevent any alarms (the instance doesn't exist any more). At first, support told me to 'delete after 30 days', which makes sense at a quick glance, but doesn't actually work; the instance doesn't exist, so there is no incoming data and hence no alerts to trigger. The 30 days is just a way to preserve data in case the instance comes back (failed hardware, or intermittent service, etc). This means that you c
  14. I submitted an enhancement for the CiscoQoS datasource, but until LM processes it you can import this. The existing version creates an instance for (QoS object + QoS Class +Qos Policy) * interfaces, so a single switch can easily have 5000+ instances. I added some properties during Active Discovery that you can use to filter based on policy direction, interface type, interface name/desc, or class name/desc. By default it only adds policies applied in the outbound direction (shaping traffic). auto.qos.interface.name auto.qos.interface.desc auto.qos.interface.type auto.
  15. I'm interested as well (for mnagel's PSIRT beta). Submitted feedback request also.