ContributionsMost RecentMost LikesSolutionsRe: SOLR JVM Stats (non-JMX) 16 minutes ago, Brandon said: Do the instances at least get discovered? If so, could you do a poll-now and shoot me the error? I'm curious as to what the issue is. The instances don't get discovered so I cannot run a manual poll. Re: SOLR JVM Stats (non-JMX) 4 minutes ago, Brandon said: Hey @George Bica! Did you get any of the other datasources to work? @Brandon I have an older version of this datasource, and it's working. Waiting on the new one to be approved to test. Solr Collection Status is for SOLR 6.6. I am testing this on one instance and it;s throwing an error when I test the script "Failed to execute the script - 2" Re: SOLR JVM Stats (non-JMX) waiting to hear back from LM security on approval so this can be installed. Re: Apache Solr datasources need scrubbing @Brandon Thank you for all these contributions on behalf of all LM community, I will give them a g. We have a lot of SOLR instances and these may prove useful for analytics. Re: Apache Solr datasources need scrubbing We have the following SOLR datasources imported but they are not finding the instances. Solr JVM Stats Applies to: solr.port && solr.append Apache_SOLR_* (many) applies to: jmx.ports How do we make the Apache_SOLR_* datasources recognize SOLR instances? They seems to depend on the jmx.ports value, but 8983 is not correct. Re: Apache Solr datasources need scrubbing 5 minutes ago, George Bica said: Where do we set the jmx.port property, in each device instance? Where do we set the jmx.port property, in each device instance? and what should the value be? The standard SOLR port is 8983 Re: Apache Solr datasources need scrubbing Where do we set the jmx.port property, in each device instance? Re: VMware vCenter monitor VM disk space alerts @Michael Rodrigues I think what you provided is correct, not sure how this was before, maybe an older version of this datasource had it the other way around. I changed the "applies to" to vCenter instead of ESX hosts and hopefully this is the correct datasource. Thank you! Re: SDT scheduling using REST API and PowerShell On 12/7/2017 at 2:22 PM, bellarmin.c said: Hi George, I am looking for device SDT which it can read devices from txt file. I tried to modify the above script and getting below error. Could you help me on it. I am looking the solution to read the device names from txt file and making it in to sdt. Getting below output Status:1007 Response: <# account info #> $accessId = 'XXXXX' $accessKey = 'XXXXX' $company = 'XXX' # stdTYpe (integer) # 1 - one time, 2 - Weekly SDT, 3 - Monthly SDT, 4 - Daily SDT # we have to use "one time" style values because LM has no concept of day of month $stdTYpe = 1 # type (string) # ServiceGroupSDT, DeviceGroupSDT, CollectorSDT $type = "DeviceSDT" # deviceGroupId (string) # $deviceDisplayName = 'hostname' # dataSourceId (integer) # 0 = ALL #$dataSourceId = 0 <# request details #> $httpVerb = 'POST' $resourcePath = '/sdt/sdts' # maintenance start $maintenancestart = "07/12/2018 11:30:00" #maintenance length (in minutes) $maintenancelength = 30 $startDate = (Get-Date -Date $maintenancestart).ToUniversalTime() $startDateepoch = [Math]::Round((New-TimeSpan -start (Get-Date -Date "1/1/1970") -end $startDate).TotalMilliseconds) $endDate = $startDate.AddMinutes($maintenancelength) $endDateepoch = [Math]::Round((New-TimeSpan -start (Get-Date -Date "1/1/1970") -end $endDate).TotalMilliseconds) # device group data $data = '{"sdtType":'+$stdTYpe+',"type":"'+ $type +'","devicename":'+ $deviceDisplayName +',"startDateTime":'+ $startDateepoch +',"endDateTime":'+ $endDateepoch +'}' <# Construct URL #> $url = 'https://' + $company + '.logicmonitor.com/santaba/rest' + $resourcePath <# Get current time in milliseconds #> $epoch = [Math]::Round((New-TimeSpan -start (Get-Date -Date "1/1/1970") -end (Get-Date).ToUniversalTime()).TotalMilliseconds) <# Concatenate Request Details #> $requestVars = $httpVerb + $epoch + $data + $resourcePath <# Construct Signature #> $hmac = New-Object System.Security.Cryptography.HMACSHA256 $hmac.Key = [Text.Encoding]::UTF8.GetBytes($accessKey) $signatureBytes = $hmac.ComputeHash([Text.Encoding]::UTF8.GetBytes($requestVars)) $signatureHex = [System.BitConverter]::ToString($signatureBytes) -replace '-' $signature = [System.Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes($signatureHex.ToLower())) <# Construct Headers #> $auth = 'LMv1 ' + $accessId + ':' + $signature + ':' + $epoch $headers = New-Object "System.Collections.Generic.Dictionary[[String],[String]]" $headers.Add("Authorization",$auth) $headers.Add("Content-Type",'application/json') <# Make Request #> $response = Invoke-RestMethod -Uri $url -Method $httpVerb -Body $data -Header $headers <# Print status and body of response #> $status = $response.status $body = $response.data| ConvertTo-Json -Depth 5 # Write-Host "Query:$response" Write-Host "Status:$status" Write-Host "Response:$body" I just realized I am not following my own post. What is the error message? VMware vCenter monitor VM disk space alerts Previous versions of VMware datasources had the ability to monitor disk space for VMs via vCenter. Looks like this ability has disappeared after LM fixed a datasource bug in January. We now have 100+ VMs that we monitor via vCenter but no alerts for their disk space. Is this something we are missing by accident, or has LM stripped this functionality on purpose?
Top ContributionsRe: Dependencies or Parent/Child RelationshipsRe: SOLR JVM Stats (non-JMX)Re: SOLR JVM Stats (non-JMX)Re: SOLR JVM Stats (non-JMX)Re: SDT - nth weekend/day supportRe: VMware vCenter monitor VM disk space alertsVMware vCenter monitor VM disk space alertsRe: SDT scheduling using REST API and PowerShellRe: SDT scheduling using REST API and PowerShellRe: SDT scheduling using REST API and PowerShell