Matthew_Dunham
Joined 9 years ago
User Profile
User Widgets
Contributions
Re: !!! Collector Debug Console Security !!!
Hi @Cole McDonald - The LogicMonitor Collector runs jobs using the permissions it has inherited from the Collector. Where the Collector is run as a privileged user so will the jobs that it's launched. Regardless of which Collector permissions model you adopt, as a best practice we recommend using our role-based access controls to limit "Manage" access to your Collectors. You can do so by assigning individuals that don't need Collector Debug functionality the "manager" role rather than the "administrator" role. This allows you to effectively limit the scope of your end-users based on the principle of least privilege.5Views0likes0CommentsRe: Datapoint - Metric type - counter - without "rate/sec math"
Hey Jamie - Good point. As a workaround, you can create a Complex Datapoint (https://www.logicmonitor.com/support/datasources/creating-managing-datasources/complex-datapoints/) to do what you need. We maintain the datasource pollling interval as a token you can substitute into your complex datapoint expressions. Provided your units are per-second (or converted as such) you can translate your "rate datapoint" into a "difference datapoint" using something like: rate_datapoint * ##POLLINTERVAL## A little more detail on substitution tokens available in datasources creation are available at: https://www.logicmonitor.com/support/datasources/creating-managing-datasources/tokens-available-for-data-collection/ Hope this helps.1View0likes0CommentsRe: Converting Octets to Mbps/Kbps
An octet is really just a fancy name for a "byte". So if you multiply this number by 8 you get bits -- that solves part of your question. The other trick is that you need to convert the point-in-time octets measurement to a rate with units of octets/sec (and eventually bps). In LogicMonitor you can do so by using the "counter" or "derive" datapoint type. See https://www.logicmonitor.com/support/datasources/creating-managing-datasources/normal-datapoints/ for details, but the short version is that these two datapoint types subtract the current value from the previous value and then divide by the configured polling interval to give you a measurement in units/sec. Then to do the multiplication above, you can use a Complex Datapoint to translate bytes/sec (octets/sec) to bps https://www.logicmonitor.com/support/datasources/creating-managing-datasources/complex-datapoints/. LogicMonitor graphs can auto-scale for you, so we'll handle the Kbps / Mbps / Gbps conversion for you as needed. For Fortinet gear, you might also have a look at our "Fortinet Fortigate Interfaces" LogicModule -- it does all this for you (and more).1View0likes0CommentsRe: Collector could not verify/register if using Palo Alto SSL decryption feature
Note that LogicMonitor does not endorse running Collectors with the EnforceLogicMonitorSSL configuration item set to "false". This setting disables certificate verification the Collector uses to authenticate our service platform before sending sensitive data. By disabling this, you risk exposing the data your Collector sends upstream to a man-in-the-middle attack. Where a decryption proxy is in use, we recommend that you disable proxying for Collector traffic as Mike specifies above.2Views0likes0CommentsRe: LM Collector API - Mask sensitive properties (i.e. password and *.pass properties)
Hi Joe - Thanks for the suggestion. That's maybe a reasonable improvement to the Collector Properties feature set. Wedesigned Collector Properties primarily to assist in the diagnosis and identification in the context of Collector Down notifications, so we wouldn't have expected a use-case by which they're used to store credentials or other sensitive information. Would you mind explaining your use-case so we can get some additional context?1View0likes0CommentsRe: PSA: Collect from windows systems without admin rights
Thanks Eric! I have been attempting to engage withthe Microsoft mothership on this issue for some timeand getting the brick wall. We'll investigate this solution and integrate into our Windows Collectors as appropriate.21Views0likes0Comments