Integration with Splunk
For this integration, we will utilize Splunk’s HTTP/HTTPS Event Collector (HEC).
The initial steps involve configuring Splunk to receive JSON data from the Mugnsoft Integrator. This entails creating an index named Mugnsoft in Splunk, enabling the HEC, and generating an access token. Subsequently, we will set up a Mugnsoft integrator component to forward monitor data to the designated Splunk instance.
Configure Mugnsoft’s integration with Splunk
Create the Mugnsoft index
Before you enable Http Event Collector, let’s define the index that will store our Mugnsoft’s monitors’ event.
- Click Settings > Indexes.
- Click New Index.
- Give it the following name Mugnsoft. Please give that exact index name.
- Save that Index.
Enable HTTP Event Collector
Before you can use Event Collector to receive events through HTTP, you must enable it. For Splunk Enterprise, enable HEC through the Global Settings dialog box.
- Click Settings > Data Inputs.
- Click HTTP Event Collector.
- Click Global Settings.
- In the All Tokens toggle button, select Enabled.
- (Optional) Choose a Default Source Type for all HEC tokens. You can also type in the name of the source type in the text field above the drop-down before choosing the source type.
- (Optional) Choose a Default Index for all HEC tokens.
- (Optional) Choose a Default Output Group for all HEC tokens.
- (Optional) To use a deployment server to handle configurations for HEC tokens, click the Use Deployment Server check box.
- (Optional) To have HEC listen and communicate over HTTPS rather than HTTP, click the Enable SSL checkbox.
- (Optional) Enter a number in the HTTP Port Number field for HEC to listen on. Note: Confirm that no firewall blocks the port number that you specified in the HTTP Port Number field, either on the clients or the Splunk instance that hosts HEC.
- Click Save.
Create an Event Collector token
To use HEC, you must configure at least one token.
- Click Settings > Add Data.
- Click monitor.
- Click HTTP Event Collector.
- In the Name field, enter a name for the token.
- (Optional) In the Source name override field, enter a source name for events that this input generates.
- (Optional) In the Description field, enter a description for the input.
- (Optional) In the Output Group field, select an existing forwarder output group.
- (Optional) If you want to enable indexer acknowledgment for this token, click the Enable indexer acknowledgment checkbox.
- Click Next.
- (Optional) Confirm the source type and the index for HEC events.
- Click Review.
- Confirm that all settings for the endpoint are what you want.
- If all settings are what you want, click Submit. Otherwise, click < to make changes.
- Copy the token value that Splunk Web displays (we will need it when configuring Mugnsoft’s integrator).
Add/Update the Mugnsoft integrator with Spunk info
- First navigate to the component web page.
- Edit the Integrator component and save.
Update or add a Mugnsoft integrator component with Spunk info and the freshly created token. Do not forget to check the Enabled box.
Check your Splunk’s Search & Reporting dashboard
You will start receiving some events in Splunk.
Copy/paste the below SPL to get some statistics on your monitors global average response time.
index="Mugnsoft" name != '' | where isnull(transactionName) | stats avg(responseTime) as avg_responseTime by name | eval avg_responseTime=round((avg_responseTime),2) | rex field=name "'(?<name>.*)'" | rename name as "Monitor Name" | sort -avg_responseTime | rename avg_responseTime as "avg response time (sec)"
Example of Mugnsoft Splunk dashboard
We can provide an example Mugnsoft Splunk dashboard. Please contact us.
Disable the Mugnsoft/Splunk integration
If you want to stop sending the monitors’ data to Splunk. Edit the integrator component and uncheck the “Enabled” checkbox.