Kerry_DeVilbiss
EmployeeJoined 9 years ago
User Profile
Employee
User Widgets
Contributions
Tesla Motors LogicModule Suite
I previously published a datasource for Tesla Motors Battery Statistics - which presents compelling vehicle battery and charging information that is fetched from the Tesla REST API. To complement those efforts, I've written a few other Tesla Motors LogicModules that return a variety of different, but still interesting, datapoints - including a ConfigSource that displays configuration information about the vehicle itself (are the doors locked? Is the sunroof open?) The following is a list of all the Tesla Motors LogicModules now available (see the above-linked post for additional info on how this all works.) DataSource 'Battery Statistics' tracks battery and charger performance and health metrics Tesla Motors Battery Statistics previously posted to the Exchange but included here for sake of keeping everything together.) The datasource name is TeslaMotors_BatteryStatistics and has lmLocator DXLLKY. DataSource 'Climate Statistics' tracks inside and outside temperatures, as well as driver and passenger temperature settings. The datasource name is TeslaMotors_ClimateStatistics and has lmLocator YZRWXC. ConfigSource 'Car Configuration' collects textual configuration data, cleans it up and makes it easily readable (screenshot attached.) The configsource name is TeslaMotors_Configuration and has lmLocator GRY9AE. DataSource 'Location Data' tracks compass heading, latitude and longitude, and power. The datasource name is TeslaMotors_LocationData and has lmLocator AYWYWA. DataSource 'Odometer Reading' does exactly what you might expect. The datasource name is TeslaMotors_BatteryStatistics and has lmLocator HHJRD91Views12likes5CommentsTesla Motors Battery Statistics
UPDATE: Check out the full suite of Tesla LogicModules in a more recent community post - including statistics for battery/ charging, climate, location, odometer, and configuration. Tesla Motors provides owners of their vehicles with a web portal - and an HTTP REST API - that can be used to retrieve vehicle performance and configuration data (in JSON format.) Using the embedded Groovy scripting functionality of a LogicMonitor DataSource, we can query the Tesla API - and bring that data back into LogicMonitor. Once we have the data, we can display it in meaningful ways (a dashboard for our Dashboards,) or perform calculations to create complex datapoints - like tracking "Average Energy Cost per Mile." Assuming that you’re not getting the electricity for free at a Tesla Supercharger station, that is... A little Googling will assist with the API key retrieval - there are a couple of scripts and/ or CURL commands that can be used to facilitate this process. The datasource name is TeslaMotors_BatteryStatistics and has lmLocator DXLLKY. Screenshot of some included graphs:35Views5likes1CommentRe: Microsoft Teams
@AJ Acevedo - our documentation team is ahead of our product team at the moment, but this will be released shortly. (I believe it's set for v.170.) Here's an early look at the docs we have published: Microsoft Teams Integration Overview Microsoft Teams Integration Settings14Views2likes0CommentsRe: Microsoft Teams
Although we don't typically make any hard and fast commitments to Product roadmap, I reached out to our Product Manager for Integrations and was told we are targeting early 2022 for Microsoft Teams, assuming all goes well... ! Hopefully just a little while longer...0Views0likes0CommentsRe: PowerShell SDK
Hey @Mark Hensler - these aren't full SDKs, but there are a couple of PowerShell modules built by customers/ staff that you might check out: https://www.powershellgallery.com/packages/LogicMonitor/1.0.1.76 (written by @mhashemi) https://www.powershellgallery.com/packages/Logic.Monitor/3.4.1 (written by @Steve Villardi)4Views3likes0CommentsLDAP Binding Security - Active Directory Domain Controllers
In December of 2019, Microsoft published a release announcing upcoming changes to LDAP channel binding and LDAP signing requirements for domain controllers. Quote There is a vulnerability in the default configuration for Lightweight Directory Access Protocol (LDAP) channel binding and LDAP signing that may expose Active directory domain controllers to elevation of privilege vulnerabilities. Microsoft Security Advisory ADV190023 address the issue by recommending the administrators enable LDAP channel binding and LDAP signing on Active Directory Domain Controllers. This hardening must be done manually until the release of the security update that will enable these settings by default. Microsoft intends to release a security update on Windows Update to enable LDAP channel binding and LDAP signing hardening changes and anticipate this update will be available in March 2020. This is a good thing (!) , as one Microsoft blogger puts it: Quote If I told you that there was a 90% plus chance that your Domain Controllers allowed receiving credentials in clear text over your network, you would probably wouldn't believe me. If I went a step further and told you that nearly half of the customers I visit for AD security assessments not only allowed them, but had extremely privileged accounts such as Domain Admins credentials traversing the network in clear text, you would probably think "that wouldn't happen on my network", well that's what they all told me too However ... security requires preparation, and this particular change means Windows administrators will want to configure servers before the patch is applied. If you're managing dozens or hundreds of servers, identifying which resources need attention could be a time consuming proposition. Luckily (per the post above) we have a couple methods to look for vulnerable domain controllers. So, with that in mind, the LogicMonitor DataSource Win_LDAP_Binding_Security uses PowerShell (specifically, Get-WinEvent) to comb through the (first 10,000 events of) Directory Services log for the presence of events with Event IDs 2886 and 2887 (and generates an alert if it finds anything.) Which again, means: Quote If any of your Domain Controllers have the 2886 event present, it indicates that LDAP signing is not being enforced by your DC and it is possible to perform a simple (clear text) LDAP bind over a non-encrypted connection. Our next port of call is the 2887 event. This event occurs every 24 hours and will report how many unsigned and clear text binds have occurred to this DC. If you have any numbers greater than zero, you have some homework to do. Hopefully this saves somebody some time - and helps bring visibility to a potentially important security vulnerability in the network! Win_LDAP_Binding_Security should be available shortly via locator code FJDAJZ154Views2likes6CommentsRe: SonicWall ConfigModule
Hey @adilorenzoPrivia, Looks like we are about to release version 2.0 of the SonicWall ConfigSource - when your account gets updated to v.129 (updates are happening over the next week), you can import it from the ConfigSource repository. Hope that helps ... should be just around the corner! Cheers, Kerry5Views1like0CommentsRe: Custom HTTP Integrations and refresh/update oauth2 tokens
Hey @PeterMattsson, I think we've had folks run into this before, it sounds familiar. Tokens can be used pretty extensively in a Custom HTTP Integration, so in theory, you could do something like: Write a scripted DataSource (applied to a Collector or other 'dummy' resource) that goes through the OAuth2 token refresh flow with the external API (we can help find an example of an OAuth flow if needed) Have this same scripted DataSource reach out to the LogicMonitor API and set the token as a property at the root of the account / wherever (auto.integration.api.key) Use the custom property value as a token in the API authentication of your Custom HTTP Integration (##auto.integration.api.key##) Takes a little bit of work - but should get the job done. Hope that helps. Cheers, Kerry47Views2likes0CommentsRaspberry Pi Core Temperature (SSH DataSource)
I was recently attempting to use a Raspberry Pi 4 as a streaming/ display mechanism for 1080p security camera footage - when I noticed a little temperature gauge flashing at the top of the display. Gee, I thought, it would sure be swell if: a) I knew what that meant, and 2.) I had some visibility into the temperature of this Pi, so I don't burn yet another hole in my workbench. Thus was born RaspberryPi_CoreTemperature, an SSH-based datasource that uses the VideoCore General Command (vcgencmd) to monitor the core temperature of a Raspberry Pi. This module was developed on Buster, the command is also present in previous builds of Raspbian. Locator Code: Y6EY626Views1like0Comments
Groups
Inner Circle
Welcome to the Customer Showcase, sponsored by “The Inner Circle “. Feel free to peruse this Customer Story Showcase to read more about what our customers are doing out in the world and how LogicMonitor is supporting their journeys.11 Posts
