The user asked if there was a way to get more than 14 days of history in the ‘Incidents' window and more than 1-hour of history in the 'Events' view. The response was that ‘Incidents’ this is not possible, however ‘Events’ can be increased by increasing RAM, which will increase the console footprint. The user then asked if a feature request could be sent for ‘Incidents’ history window. The response was that this could be done, although the audit data can be sent to syslog server in order to query for more than 14 days.
Read the entire article here...
Databases Related Training & Support Archives
Databases training and support-related archives from inside the ControlUp Community on Slack.
Where Does ControlUp Solve Get Its Data?
A user asked why Solve was displaying data and where it was being sourced from - it was clarified that it came from Monitor In-RAM DB and could also be accessed programmatically with the Monitor Cluster Cmdlets.
Read the entire article here...
Read the entire article here...
Reporting Poor Connections in ControlUp
A user asked for suggestions on how to report on user connections with poor latency, signal strength, and RTT. They could utilize the Network Dashboard to report on top bad latency, longest traceroutes, plus pull data from Configuration > Data > device_status and set alarms to alert on select fields. They can also export the data from ControlUp into MS Excel for more complex reporting. Futhermore, more features are in the roadmap to expand reporting in the future. Links to two articles were provided for more information.
Read the entire article here...
Read the entire article here...
How does ControlUp report failed logins in the logon duration report?
ControlUp users were discussing how to determine failed logins for the Logon Duration Report, and the root cause of the issue: the Antivirus product scanning thousands of files stored in the Roaming profile. The current FSLogix release was mentioned to be 'trash', while UPM has been known to work better with one issue. Citrix has been asked to incorporate a work-around in a future UPM release to solve the issue.
Read the entire article here...
Read the entire article here...
Investigating Unexpected Alert Triggers in ControlUp
A problem occurred when seemingly unrelated events caused the trigger monitoring the lab's pools to be reset and send off alerts. It seems to have been caused by a logged-out and then logged-back-in monitor service account. It is being investigated if something else forced the logout or if it is expected behaviour. To stop alerts from firing when the account signs back in, it is suggested to uncheck the "Include folders that were just discovered" checkbox. As the monitors use an in-ram database, if restarted the previous states are not remembered.
Read the entire article here...
Read the entire article here...
Customizing Widgets and New Analytics in ControlUp Solve
The conversation began with customers asking for the ability to filter applications in widgets, blacklisting or whitelisting them. ControlUp is now excluding ControlUp processes and allowing customization of widgets in the upcoming Solve release. In addition, there will soon be a new analytic report for machines with high CPU. Finally, users can use Export-CuQuery to create a workaround to get data on applications crashing or hanging.
Read the entire article here...
Read the entire article here...
How are the credentials saved on ControlUp Scoutbees for a published App/Desktop scout?
Credentials for Apps/Desktops on Scoutbees are encrypted either in a database or with AWS-vault, depending on whether the Scout is running on a cloud hive or a custom hive. When configuring a custom hive, the credentials are stored only locally in a file. For further information see https://controlupcommunity.slack.com/archives/C046DUGB6M9/p1668549692870029.
Read the entire article here...
Read the entire article here...
ControlUp Edge DX Data Storage Limits and Options Explained
The user noticed Edge only keeps data for 30 days and asked for an explanation, as they had options to view data from earlier in the year. @member clarified that Edge keeps data for up to 30 days, occasionally longer if storage is available, and suggested the user supply a screenshot so the issue can be replicated. @member investigated further and found session data from August, but the user still noticed other data going back to May. The user suggested the "This Year" option is unnecessary and unlikely to display data older than 30 days.
Read the entire article here...
Read the entire article here...