Feature Request: Website Properties
Two requests: 1. Website Inherited Properties Please could the website entity have an “inheritedProperties” field added, much like resources do. This will not require any additional UI, but saves a lot of API round trips. 2. Website Custom Properties Please could the website entity have an “customProperties” field added, much like resources do. This WILL require additional UI on the Website Create/Edit Dialog. Happy if this is UIv4 only.25Views13likes4Commentssuggtion: Veeam monitoring via REST API
hi, the doco for monitoring Veeam says that only Veeam Backup Viewer access is required, but Backup Administrator is actually required when using the underling PowerShell module. The REST API doesn't require admin privileges, may i suggest updating the LogicMonitor module for Veeam to use the API? https://www.logicmonitor.com/support/monitoring/backup-and-replication-systems/veeam-backup-replication-monitoring https://helpcenter.veeam.com/docs/backup/powershell/getting_started.html https://helpcenter.veeam.com/archive/backup/120/vbr_rest/reference/vbr-rest.html40Views8likes2CommentsGetting specific datapoints using the REST API
In this post: https://community.logicmonitor.com/archive-13/getting-datapoint-data-via-rest-api-1249 … @Sarah Terry provides information on how to get data for just specific datapoints, reducing load on the API, minimizing network traffic and reducing deserialization load on the client. While this is VERY useful, it is not currently possible to do this for graph data. An example of such a call would be: {{logicmonitor_url}}/device/devicedatasourceinstances/229505122/graphs/-1/data?datapoints=sentpkts …which brings back the default graph data (all datapoints), though this would also work for a specific graph. The advantage of this approach to data fetch is that it permits the retrieval of virtual datapoints. In order to achieve the same benefits, we (Panoramic Data) request that the same datapoint filtering is added to the {{logicmonitor_url}}/device/devicedatasourceinstances/{instanceId}/graphs/{graphId}/data endpoint. Of lesser importance would be other graph API endpoints (e.g. the website graph API endpoint) Thanks in advance! David35Views15likes0Comments[Feature request] Custom PowerShell script: increase timeout
Hello, I was advised to go here after chatting with support. I have run into an issue where our custom PowerShell script runs into the hardcoded 120 second timeout. We're initially testing it first via the Test button. The error after exactly 120 seconds is: “"Test script failed - no response was received from the Collector"”. The script runs okay in PowerShell 5.1, but it averages around 2,6 minutes. We have already cut the runtime down from around 4 minutes to 2,6 minutes and that's the best we can do. It starts generating “Write-Host” data within 50 seconds for each object. We are pulling data from public API endpoints and perform some logic for 2 large arrays. The script will run against a dedicated collector. Issue is in the sandbox as well as in the production environment.Solved102Views13likes7Comments