chrisred
NeophyteJoined 2 years ago
User Profile
Neophyte
User Widgets
Contributions
Re: Modules for Citrix Cloud/DaaS/VAD monitoring
Hi jgillotti I would make sure the monitor is using the correct Citrix API endpoint address (should be the IP/DNS name for the device its running on). One of these: api-ap-s.cloud.com – Asia Pacific South api-eu.cloud.com – European Union api-us.cloud.com – United States api.citrixcloud.jp – Japan You could also try loading one of those addresses in a browser on the Collector running the monitoring, and see if there is an SSL error. Usually an error like this will be due to a firewall doing SSL inspection and breaking the certificate chain.81Views1like0CommentsA Push Connector for ServiceNow Event Management
Hi, this is a Push Connector for ServiceNow Event Management. If you are looking to send alerts from LogicMonitor to the Event Management feature this may be helpful. There is a connector for LogicMonitor created by ServiceNow, but it has a number of issues. Some fields are not mapped well to the ServiceNow event, website alerts for example have multiple fields not populated. It doesn't properly handle the non-standard date format LM uses in the alert tokens, and certain time zone identifiers like "BST" or "CST" cause the connector to "crash". This one fixes those issues and does some better mapping for the event fields, additional details are in the repository linked below. https://github.com/chrisred/snow-itom-push-connectors97Views1like0CommentsRe: Azure LogAnalytics Workspaces datasources
Not at DataSource, but you could look at the "Azure Site Recovery" official EventSource. This uses the "Azure Log Analytics Workspaces" collection method, which has a kusto query configured. I asked support about whether it was possible to use that collection method for our own custom EventSources. They said it wasn't supported. I played around with returning different fields, but with it being undocumented and support being evasive i gave up. Maybe it is the same situation with the DataSource, it has the option to configure a query, but no information on how it is supposed to work.63Views0likes0CommentsRe: Modules for Zerto monitoring
I have updated the the "ZertoAppliance" modules to support the Linux appliance authentication, with help from Bhavesh. The updated files are in the Github repo. zertoappliance.api.id and zertoappliance.api.key set the client id/client secret credentials configured in Keycloak: https://help.zerto.com/bundle/Linux.ZVM.HTML.10.0/page/Creating_Keycloak_Credentials.htm zertoappliance.port is set to 443 by default, and this automatically chooses the Linux authentication method. Setting any other port will choose the Windows authentication method, 9669 is the default for Windows. If there is a Windows appliance running on port 443 (or Linux not running on 443) zertoappliance.type can be used for force the authentication method to either "linux" or "windows".158Views1like0CommentsRe: Modules for Citrix Cloud/DaaS/VAD monitoring
Hi Dave_Lee , This is probably due to log on activity in the delivery groups. By default the DataSource will capture sessions started in a 4 hour period, and it will only calculate the averages when there are at least 3 sessions started within the 4 hrs. So low log on activity in a delivery group will mean "No Data" and gaps in the graph. I suspect that is the issue. In the notes section of the DataSource there is more explanation and properties for tuning. You could use the "citrixdass.logonsearch" property to increase how far back sessions will be captured.157Views0likes0CommentsRe: 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.279Views2likes0CommentsRe: 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.270Views1like0Comments