Open-Source Software libraries used within this add-on include:
For technical support, questions or concerns on the release --
contact our development team at support@catchpoint.com.
Technical Note
app.conf overview: $SPLUNK_HOME/Splunk/etc/apps/search_cp/local/app.conf
Upon initial setup, the parameter is configured located under the stanza install must have a value of 0. This value represents that the application is indeed starting up for the first time and is not configured for use. A user's first use of the Catchpoint Splunk Modular Input should, by default, take the user to the App configuration page when the is configured is 0.
From the home view of SplunkWeb, navigate to the left-hand side and select the grayed Find More Apps icon. In the search bar that appears, search for Catchpoint Search and select Install. Upon completion, select Restart. Once restarted, from the home view, select the Catchpoint Search app found on the left-hand side of the view. On the App configuration page which follows, select Continue to app page setup to continue.
On the setup page, the base URL (Catchpoint API URL) has been automatically set.
Complete the setup by supplying the consumer key and consumer secret within the remaining fields.
Multiple client/division support for performance and alerts data:
1. To pull data from multiple client/division, Navigate to Manage Apps page.
1. Search for Catchpoint Search and select Set up from Actions.
1. Complete the setup by supplying the consumer key and consumer secret within the remaining fields.
If manually installing the application from its tarball form, it is important to ensure (when the .tar has been expanded) that the base directory's name of the application is search_cp.
The end result of a manual installation should reflect the following folder structure -- where search_cp is the name of the application directory.
~SPLUNK_HOME
\etc
..\apps
..\..\search_cp
Navigate to Settings > Data inputs and locate Catchpoint Modular Input. On the right-hand side of the located row, select Add New. To begin ingesting Catchpoint data within Splunk, supply the required values for Catchpoint Input Name, Test ID and Client Secret, Catchpoint Input Name is used only for labeling the tests json. Client Secret should match one of the consumer secret key which was supplied in the set up page.
It should be noted that the user should pay special attention to the required format of the Test ID field.
The modular input can be setup with just one test ID, however, if the user chooses to create the modular input with multiple test IDs,
it is required multiple test IDs
Example.
Assume the following Test IDs to be of the same type:
Assume the following Test ID to be of a different type of the IDs mentioned above:
As an example,
https://io.catchpoint.com/v{version}/performance/raw?tests=XXX,YYY,ZZZis a VALID endpoint because
As a closing example,
https://io.catchpoint.com/v{version}/performance/raw?tests=XXX,BBB,YYYis an INVALID endpoint because although
Options
Under More settings, the user is able to set the Index and Host field values.
The Index dropdown sets the destination index for this source. It is recommended users choose catchpoint as the specified index. To finish input setup, select Next toward the top of the page's view.
Closing Note
The frequency or 'interval' of how often the newly created data input is executed has been programmatically determined by using the start and end time values of the initial event json recently indexed into Splunk.
Upon completing the Getting Data In section, the user is now ready to view thier data being ingested within Splunk. From Splunk's homepage, select the Catchpoint Search app icon found on the left-hand side.
The user is able to complete searches within the Catchpoint index with the command index = catchpoint.
- Extended support for Python 3 and SplunkLib version 1.6.14.
- Added multiple division and client support for performance and alerts data.
- Changed the parsing logic to pull more metrics from REST API response.
- Added Catchpoint insight data to Splunk.
Fixed defect where transaction steps were shown as null.
Improved dashboard usability.
Added ability to pull Catchpoint alert data.
Removed Catchpoint Index per Splunk guideline that Apps should not create indexes.
Improved dashboard visualizations.
Fixed defect that prevented authentication to Catchpoint API if credentials initially incorrect and updated to be correct.
Initial release allows retrieving Catchpoint raw synthetic test performance data.
Splunk AppInspect evaluates Splunk apps against a set of Splunk-defined criteria to assess the validity and security of an app package and components.
As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 10GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps and add-ons from Splunk, our partners and our community. Find an app or add-on for most any data source and user need, or simply create your own with help from our developer portal.