Skip to content

Commit 2f22da1

Browse files
committed
Update Blog “integrating-hpe-greenlake-webhooks-with-splunk”
1 parent 42d4936 commit 2f22da1

File tree

2 files changed

+29
-21
lines changed

2 files changed

+29
-21
lines changed

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

Lines changed: 29 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "Integrating HPE GreenLake webhooks with Splunk "
33
date: 2025-06-24T11:34:04.977Z
44
author: Vandewilly Silva
5-
authorimage: /img/Avatar1.svg
5+
authorimage: https://ca.slack-edge.com/E01LD9FH0JZ-U05UA6N7KH6-6b8619b87acd-512
66
disable: false
77
tags:
88
- hpe_greenlake_cloud
@@ -15,6 +15,7 @@ li {
1515
max-width: none;
1616
}
1717
</style>
18+
1819
## Overview
1920

2021
This guide shows you how to connect HPE GreenLake webhooks with [Splunk](https://www.splunk.com/). Splunk is a data platform that collects, indexes, and analyzes machine-generated data to provide insights for various purposes, including security monitoring, IT operations, and business analytics. When the two are connected, you will be able to see your HPE GreenLake events through Splunk for improved data monitoring and analysis.
@@ -112,14 +113,16 @@ Let's create a custom REST endpoint handler in Python to handle the HPE GreenLak
112113

113114
### Directory structure
114115

115-
`splunk_hpe_webhook_app/
116+
```markdown
117+
splunk_hpe_webhook_app/
116118
├── bin/
117119
│   └── hpe_webhook_handler.py
118120
├── default/
119121
│   ├── restmap.conf
120122
│   └── web.conf
121123
└── metadata/
122-
└── default.meta`
124+
└── default.meta
125+
```
123126

124127
### Python handler (bin/hpe_webhook_handler.py)
125128

@@ -236,29 +239,35 @@ class HPEWebhookHandler(BaseRestHandler):
236239

237240
#### default/restmap.conf
238241

239-
`[script:hpe_webhook_handler]`
240-
`match = /hpe/webhook`
241-
`script = hpe_webhook_handler.py`
242-
`scripttype = persist`
243-
`handler = hpe_webhook_handler.HPEWebhookHandler`
244-
`requireAuthentication = false`
245-
`output_modes = json`
246-
`passPayload = true`
247-
`passHttpHeaders = true`
248-
`passHttpCookies = false`
242+
```markdown
243+
[script:hpe_webhook_handler]
244+
match = /hpe/webhook
245+
script = hpe_webhook_handler.py
246+
scripttype = persist
247+
handler = hpe_webhook_handler.HPEWebhookHandler
248+
requireAuthentication = false
249+
output_modes = json
250+
passPayload = true
251+
passHttpHeaders = true
252+
passHttpCookies = false
253+
```
249254

250255
#### default/web.conf
251256

252-
`[expose:hpe_webhook_handler]
257+
```markdown
258+
[expose:hpe_webhook_handler]
253259
pattern = hpe/webhook
254260
methods = POST`
261+
```
255262

256263
#### metadata/default.meta
257264

258-
`[restmap/hpe_webhook_handler]
265+
```markdown
266+
[restmap/hpe_webhook_handler]
259267
export = system
260268
[views]
261269
export = system`
270+
```
262271

263272
## Configuring Splunk HTTP Event Collector (HEC)
264273

@@ -292,7 +301,7 @@ The complete integration flow works as follows:
292301

293302
* Deploy the custom Splunk endpoint handler using the above HPE webhook handler Python script.
294303
* Make sure to set HEC token and webhook secret in the Python script.
295-
* Register the webhook handler URL with HPE GreenLake: <https://your-splunk-instance:8089/servicesNS/-/your_app/hpe/webhook>
304+
* Register the webhook handler URL with HPE GreenLake: [`https://your-splunk-instance:8089/servicesNS/-/your_app/hpe/webhook`](https://your-splunk-instance:8089/servicesNS/-/your_app/hpe/webhook)``
296305

297306
> 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
298307
@@ -306,10 +315,7 @@ The complete integration flow works as follows:
306315

307316
4. Data flow diagram
308317

309-
`HPE GreenLake → Custom REST Endpoint → Validation → HEC → Splunk Index`
310-
`↓           ↓                ↓      ↓     ↓`
311-
`Events     Challenge       Verify   Ingest   Analyze`
312-
` Response       Signature   Data Visualize`
318+
![Data flow diagram](/img/diagram.jpg "Data flow diagram")
313319

314320
## Benefits of this architecture
315321

@@ -327,9 +333,11 @@ Testing the integration
327333

328334
1. Verify custom endpoint: Test your custom REST endpoint using curl:
329335

330-
`curl -X POST `[`https://your-splunk-instance:8089/servicesNS/-/your_app/hpe/webhook`](https://your-splunk-instance:8089/servicesNS/-/your_app/hpe/webhook)` \`
336+
```shell
337+
`curl -X POST`[`https://your-splunk-instance:8089/servicesNS/-/your_app/hpe/webhook`](https://your-splunk-instance:8089/servicesNS/-/your_app/hpe/webhook)`\`
331338
`-H "Content-Type: application/json" \`
332339
`-d '{"type": "test.event", "data": {"message": "Hello Splunk"}}'`
340+
```
333341

334342
2. Webhook registration: Register your webhook with HPE GreenLake using the custom endpoint URL.
335343
3. Challenge validation: Monitor Splunk logs to ensure the challenge request is handled correctly.

static/img/diagram.jpg

23.6 KB
Loading

0 commit comments

Comments
 (0)