dorian_fuchs
NeophyteJoined 3 years ago
User Profile
Neophyte
User Widgets
Contributions
Re: REST API 503 errors
Hello everyone I have now received feedback from LM that on March 26, 2024 auto throttling for external API calls was activated and therefore the 503 HTTP errors are coming (nowhere mentioned in the releases note, etc.). The feedback from LM on my question how we can handle such errors in the future was simply "script a catch and try again after a certain time". What do you think about this? Is this our problem now if the API has resource bottlenecks? Is LM leaving us to our fate here? Should LM increase the resources of the API? In my opinion, a 429 HTTP error would be the right "procedure". 1. for 429 errors, the person who makes a request can do something about it AND also do something against it. 2. in the case of 503 errors, the person making the request can usually do nothing about it if there is a high load on the API AND also do nothing against it. Have a nice weekend soon Dorian14Views0likes2CommentsREST API 503 errors
Hello everyone We have been using various PowerShell scripts for years and have never had any problems with them. Now, since last week Monday, we are getting random 503 “server is busy” HTTP errors on some GET queries such as Devices, Device DataSources, Dashboards, etc. There is no recognizable pattern to the errors. Does this problem also occur for others using script automation via the REST API (occurs in V2 and V3)? I have submitted a support request to LM, but progress is slow... Have a nice day everyone Dorian109Views1like15CommentsREST API Device SLA Widget
Hi Portal I am currently automating our SLA reporting and have come across the following issue. When I create a device SLA widget via REST API, I do not have the option "displayPercentageBar". When I make an Inspect in Chrome, for example, I see this setting: However, when I set it via REST API, nothing happens. Has anyone ever had to deal with this? Greetings DorianSolved87Views9likes5CommentsRe: Modules for Citrix Cloud/DaaS/VAD monitoring
OK, you used an existing device monitoring the Cloud Connector. In that case the citrixdaas.host property should be set to the API endpoint address. So “api-eu.cloud.com” for an EU country and for other regions like the UK it should be ”api-us.cloud.com”. The region is listed in the Citrix Cloud account details if you want to double check. Yes, now everything has worked. Thanks for the support!21Views0likes0CommentsRe: Modules for Citrix Cloud/DaaS/VAD monitoring
Hi Dorian, Yes, they should be working. “Connection reset” sounds like a network issue. On the device you added the “citrixdass” properties to what IP Address/DNS Name is set? Assuming you have a DaaS/Cloud setup it should be one of the Citrix Cloud endpoints, e.g. api-us.cloud.com. The notes on the “Citrix DaaS Token” datasource have some details, if that is not running successfully the others wont either. Sorry, not quite getting there :D system.categories - Add "CitrixDaaS". citrixdaas.api.id - Citrix Cloud API Client ID. citrixdaas.api.key - Citrix Cloud API Client Secret. citrixdaas.customerid - Citrix Cloud Customer ID. -> I have set these attributes on the Citrix Cloud Connector system. What is meant by the citrixdaas.host attribute and the API regions?20Views0likes0CommentsRe: Citrix Cloud Monitoring
Hi @Tim OShea from the shown Error you are using a Wrong Service Url in your Query. Which Url do you have set in your Script? I also have problems with the DataSources again. Which URL needs to be adapted in each case? E.g. in the Logon Performance DataSource: "https://${customer}.xendesktop.net/Citrix/monitor/odata/v4/data/DesktopGroups" -> is this no longer correct? Presumably the query for this is not correct either. Unfortunately, I'm not as good at Groovy as I am at PowerShell :/2Views0likes0CommentsRe: Modules for Citrix Cloud/DaaS/VAD monitoring
Hi Chris Can these modules still be used with the new API? I used the modules from this article (https://community.logicmonitor.com/lm-exchange-29/citrix-cloud-monitoring-2682/index2.html) for a long time, but they are no longer compatible with the new API. I imported your modules and tried to test Active Discovery for different modules, but got the same error everywhere: Does anything else need to be adjusted? Thanks for checking, greetings Dorian19Views0likes0CommentsRe: LogicModule Updates in UIV4
I was able to check this today in the old diff view (last week I no longer had access to it?). My modules are not metadata that have been customized. Everywhere it was just the order of e.g. graph definitions or datapoints. It makes no sense to me that this makes a difference from the old to the new view. Or as you said, that the diff engine recognizes that something has been changed but still doesn't recognize anything😅 I have reported this to our CSM.7Views1like0Comments