Recent Discussions
Custom Properties auto-resetting after Save?
I will probably open a support ticket and I hope this is just an ignorance thing on my part, but figured I'd check first. A user reported a weird situation. They have a resource folder in which they have set a custom property (snmp.version) to be "v3". For some reason one of the devices in that folder is overriding that with a custom property where the value is set to "v2c". SO FAR NO PROBLEM. But when we either change the custom property on the resource OR DELETE the custom property, as soon as we hit SAVE, the custom property is unchanged. We set snmp.version to v3 and LM immediately sets it to v2c. We delete the custom property, in hope the v3 value is inherited as it should be, but as soon as we hit save ... NO DICE. The value is just v2c anyway. No matter how many times we go change this property (set directly) and edit it to be v2c, or delete it, as soon as we hit save, NOTHING. It the logs I see that I edited the device, but no details. Is there some weird known scenario where this happens? I've never seen anything like it. And I have ENSURED that v2c is not set on any of the other static or dynamic folders that the resource is in. Has anyone seen this before? I kind of feel silly honestly. I wanted to ask here before I bother support.
Support Cases - Conversation Timestamps Incorrect
I am trying to gather information on technical requests that have taken a considerable amount of time to resolve. While doing so, I noticed when opening a ticket with technical support (through a chat conversation), the case record shows all conversation entries at the exact same time. It appears that the date/time stamp is for the last entry in the conversation. However, if you export the chat, the timestamps appear correct: I am curious if this information is relied upon in order to identify support improvements.
Adding additional Root and Intermediate CA certificates to Linux collector.
Hello, I have some https website tests that are failing because the Root and Intermediate CA certificates are not in the collector trust store. I have added the certificates into /etc/ssl/certs and ran sudo update-ca-certificates. openssl s_client connection now verifies the certificate chain, however the website test still fails with the same error. does the collector use a different trust store to the standard package installed to the Ubuntu 22.04 OS? I'm assuming that as it's mostly Java based there is a particular module or something that uses a different trust store. I can't find any information about this elsewhere. The CA's in question are: SectigoRSADomainValidationSecureServerCA.crt SecureCertificateServices.crt /etc/ssl/certs/ lrwxrwxrwx 1 root root 19 Jul 21 17:19 75583d7f.0 -> SecureCertificateServices.pem lrwxrwxrwx 1 root root 44 Jul 21 17:19 65ff7287.0 -> SectigoRSADomainValidationSecureServerCA.pem you can see here the openssl verification of the chain: Start Time: 1753171962 Timeout : 7200 (sec) Verify return code: 0 (ok) Then the website check step failing: One other minor frustration is in the debug runner, !opssl is listed as a valid command, however when trying to run it, it says unknown debug command, really not all that useful so I can to connect to the customer environment and directly ssh to the collectors to even begin troubleshooting because there was no real useful information returned in the UI.
