Skip to content

Commit 9397808

Browse files
committed
Update Blog “integrating-hpe-greenlake-webhooks-with-splunk”
1 parent 1c5ae5b commit 9397808

File tree

1 file changed

+17
-17
lines changed

1 file changed

+17
-17
lines changed

content/blog/integrating-hpe-greenlake-webhooks-with-splunk.md

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -318,34 +318,34 @@ The complete integration flow works as follows:
318318
319319
1. Initial setup
320320
321-
* Deploy the custom Splunk endpoint handler using the above HPE webhook handler Python script.
322-
* Make sure to set the HEC endpoint in the Python script (line 13)
323-
* Make sure to set the Splunk HEC API token in the Python script (line 14)
324-
* Make sure to set the HPE GreenLake webhook secret in the Python script (line 15)
325-
* Register the webhook handler URL with HPE GreenLake:
321+
* Deploy the custom Splunk endpoint handler using the above HPE webhook handler Python script.
322+
* Make sure to set the HEC endpoint in the Python script (line 13)
323+
* Make sure to set the Splunk HEC API token in the Python script (line 14)
324+
* Make sure to set the HPE GreenLake webhook secret in the Python script (line 15)
325+
* Register the webhook handler URL with HPE GreenLake:
326326
327-
* URL of handler: [`https://your-splunk-instance:8089/servicesNS/-/your_app/hpe/webhook`](https://your-splunk-instance:8089/servicesNS/-/your_app/hpe/webhook)
328-
* Set the same secret key as we setup in the Python handler (line 15)
329-
* Use API as Authentication type and set the API key to the Splunk REST API Key generated in the section above.
327+
* URL of handler: [`https://your-splunk-instance:8089/servicesNS/-/your_app/hpe/webhook`](https://your-splunk-instance:8089/servicesNS/-/your_app/hpe/webhook)
328+
* Set the same secret key as we setup in the Python handler (line 15)
329+
* Use API as Authentication type and set the API key to the Splunk REST API Key generated in the section above.
330330
331331
> Note: See [this blog](https://developer.hpe.com/blog/getting-started-with-the-hpe-greenlake-cloud-eventing-framework/) to learn how to register a new webhook handler in HPE GreenLake
332332
333333
2. Webhook handler verification process
334334
335-
* HPE GreenLake sends a verification challenge to your custom endpoint.
336-
* The custom REST handler receives the challenge and validates it using HMAC SHA-256.
337-
* The handler responds with the computed verification hash.
338-
* HPE GreenLake confirms the webhook and marks it as active.
335+
* HPE GreenLake sends a verification challenge to your custom endpoint.
336+
* The custom REST handler receives the challenge and validates it using HMAC SHA-256.
337+
* The handler responds with the computed verification hash.
338+
* HPE GreenLake confirms the webhook and marks it as active.
339339
340340
3. Event processing flow
341341
342-
* HPE GreenLake sends event data to the custom handler endpoint.
343-
* The custom REST handler validates the HMAC signature.
344-
* The handler forwards validated events to HEC.
345-
* Splunk HEC ingests the data for analysis and visualization.
342+
* HPE GreenLake sends event data to the custom handler endpoint.
343+
* The custom REST handler validates the HMAC signature.
344+
* The handler forwards validated events to HEC.
345+
* Splunk HEC ingests the data for analysis and visualization.
346346
347347
4. Data flow diagram
348-
348+
349349
![Data flow diagram](/img/diagram.jpg "Data flow diagram")
350350
351351
## Benefits of this architecture

0 commit comments

Comments
 (0)