The IOP team is looking at upgrading Splunk to a version 9+ after a customer's security scan revealed multiple vulnerabilities for versions below 9.x. In the meantime, exceptions have been put in place. IOP is a Splunk OEM product and cannot be incorporated into another Splunk solution, and multiple support requests have been sent as well. Ref #132898.
Read the entire article here...
Splunk Related Training & Support Archives
Splunk training and support-related archives from inside the ControlUp Community on Slack.
How to Configure a ControlUp Alert Trigger for 90% of Maximum Index
A user asked how to set up an alert concerning the “Smart-X ControlUp Term License stack” with a trigger of 90% of the maximum available index. Dennis provided guidance to configure an alert if the licensed volume goes above the licensed volume using Splunk. The ControlUp version used is 8.6.0.192.
Read the entire article here...
Read the entire article here...
Changing the Certificate on the IOP Server
The user asked how to change the certificate on the IOP server - he received a .PEM file without private key and was suggested to refer to the following documents: https://support.controlup.com/docs/solve-on-premises-configuration and https://support.controlup.com/docs/insights-on-premises-replace-certificate. Finally, the certificate was implemented and the user noted that the IOP server correctly presented it but not the Splunk side.
Read the entire article here...
Read the entire article here...
Seeking Splunk Metrics for Disk IOPS Reporting on IOP Dashboards
A user was looking for the Disk Read and Write IOPS metrics for custom dashboards on IOP. Someone suggested to utilize the underlying Splunk query to customize existing reports, while another user mentioned that the metric diskreadpersec_avg is Disk Reads IOPS. More information on the other metric was requested.
Read the entire article here...
Read the entire article here...
Joining session data with client_name using session_object_guid with Splunk app usage search
The user was struggling to join session data with their search results to include the client_name as an additional column. It was determined that the process_base source should use the session_object_guid to join the session_base to find the client_name. A joining process was outlined that would filter the subset of session to less than 50k. The user asked for an example of this process and was provided with one. The final result should include date, time, username, client_name, computer_name, and process_name.
Read the entire article here...
Read the entire article here...