Skip to content

Commit 60d0070

Browse files
committed
Update Blog “getting-started-with-the-hpe-greenlake-cloud-eventing-framework”
1 parent e2f599f commit 60d0070

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

content/blog/getting-started-with-the-hpe-greenlake-cloud-eventing-framework.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,17 @@ tags:
88
- hpe-greenlake-cloud
99
- webhooks
1010
---
11+
<style>
12+
ul li{
13+
font-size:27px;
14+
}
15+
</style>
16+
<style>
17+
ol li{
18+
font-size:25px;
19+
}
20+
</style>
21+
1122
## Polling API or subscribing to events: That IS the question
1223

1324
In one of my previous blog posts, I used the HPE GreenLake API to query the audit log and, if anything appeared in the audit log over the course of the last few minutes, I arranged for it to be displayed on screen. To do this, I had to continuously poll the API at a regular polling interval. While this works, it is not ideal, since it is not real time, and you might get notified of an important event after, at max, your polling interval. A better approach that is often available on software platforms is called events, also referred to as webhooks. HPE GreenLake cloud provides this functionality and, in this post, I will explain how to leverage it.

0 commit comments

Comments
 (0)