You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: app/_kong_plugins/solace-log/index.md
+9-5Lines changed: 9 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ content_type: plugin
6
6
7
7
publisher: kong-inc
8
8
tier: enterprise
9
-
description: 'Publish request and response logs to a Solace topic'
9
+
description: 'Publish request and response logs to a Solace endpoint or topic'
10
10
11
11
products:
12
12
- gateway
@@ -52,10 +52,10 @@ related_resources:
52
52
url: /event-gateway/
53
53
---
54
54
55
-
Publish request and response logs to a [Solace](https://solace.com/) topic.
56
-
For more information, see [Understanding Solace topics](https://docs.solace.com/Get-Started/what-are-topics.htm).
55
+
Publish request and response logs in `JSON` format to a [Solace](https://solace.com/) endpoint or topic.
56
+
For more information, see [Solace Event Messaging Overview](https://docs.solace.com/Messaging/messaging-overview.htm).
57
57
58
-
Kong also provides Solace plugins for request and response transformations:
58
+
Kong also provides plugins for publishing messages to and consuming messages from Solace:
59
59
*[Solace Upstream](/plugins/solace-upstream/)
60
60
*[Solace Consume](/plugins/solace-consume/)
61
61
@@ -65,7 +65,11 @@ Kong also provides Solace plugins for request and response transformations:
65
65
66
66
## Implementation details
67
67
68
-
TBA
68
+
This plugin leverages the [log PDK](/gateway/pdk/reference/kong.log/) to collect and [customize](#custom-fields-by-lua) log fields.
69
+
70
+
The prepared log message is sent to Solace broker via the official [Solace C API](https://docs.solace.com/API/Messaging-APIs/C-API/c-api-home.htm). The sending job is executed in a background timer context, such that it would not block the client requests.
71
+
72
+
If the [custom Lua code](#custom-fields-by-lua) associated with the log fields fails to execute, the relavent fields remain untouched.
0 commit comments