-
Notifications
You must be signed in to change notification settings - Fork 635
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ISSUE#4419] Add slack sink connector. #4562
Conversation
...ck/src/main/java/org/apache/eventmesh/connector/slack/sink/connector/SlackSinkConnector.java
Outdated
Show resolved
Hide resolved
...ck/src/main/java/org/apache/eventmesh/connector/slack/sink/connector/SlackSinkConnector.java
Outdated
Show resolved
Hide resolved
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #4562 +/- ##
============================================
+ Coverage 17.01% 17.04% +0.03%
- Complexity 1660 1667 +7
============================================
Files 761 766 +5
Lines 28826 28875 +49
Branches 2494 2498 +4
============================================
+ Hits 4905 4923 +18
- Misses 23463 23492 +29
- Partials 458 460 +2 ☔ View full report in Codecov by Sentry. |
@yanrongzhen please solve the conflict. |
# Conflicts: # settings.gradle
@yanrongzhen , I'm trying to setup the Slack connector locally. Do you have an example payload that you used to send a message? I'm currently seeing this when the connector has started: I'm trying to send a message but not seeing any logs nor receiving any message. I configured the correct apiKey and also made sure the correct scopes are assigned to it. Any help would be appreciated! |
@brampurnot Sink connector retrieves data from EventMesh and sends it to a external component, which is referred to as Slack here. So you can try using Spring Source Connector to send some data to EventMesh first. Here is an example of Spring Source Connector sending data, but you need to pay attention to two points. Firstly, you need to configure If there are still any issues, we look forward to @yanrongzhen 's reply. Or there may be a more convenient way, and we also look forward to @yanrongzhen 's reply. |
Thanks @pandaapo for your reply. I assume we can also use the HTTP channel to publish a message view a CloudEvent to event mesh which will be then be picked up by slack, right? Or is this not possible? |
@brampurnot This should also be possible, but there may be some requirements for CloudEvent object. This requires a response from the author @yanrongzhen or other members of the community. |
This is possible, just need to start the EventMesh runtime and slack sink connector, the messages sent by the HTTP channel will be picked up by slack. |
Ok I was able to make it work. Seems like the JAR that gets generated is having issues. I do have another issue but I'll create a new incident for it since I'm having the same issue in the mongoDB connector. |
Could you provide a detailed description of the issue with generating JAR?
Could you also provide a detailed description of this issue? |
I'm not 100% sure what the problem is. But it basically stops without showing any logs anymore when I run the JAR from the dist/plugin/connectors folder. I basically compiled it from scratch and ran it directly from within VS Code and then it works fine. I still need to figure out what the problem is since I want to run it in a container. Now the connector is up-and-running and when I try to post a CloudEvent over the HTTP channel, I'm getting a NPE. This is what I see in the event mesh server:
I assume it's related to the message I'm posting but still trying to figure out exactly what is wrong. Bram ps: sorry guys I know I'm asking/trying a lot but I'm trying to setup a simple POC :) |
I'm trying to use the following message body btw:
|
Just an FYI - I managed to make it work with the Java SDK. However when posting a CloudEvent directly to the HTTP channel, I'm still getting a NPE. |
Sorry for not responding to your comment for a while. Are you still experiencing any issues? You can create a new |
Sorry for the delay. It's been a while since I looked into this but I was just about to pick it up again. I can confirm we still have the issue. |
Here are some log statements:
|
I am unable to reproduce this issue on the latest version. Based on the two logs you posted, it seems that you are experiencing this issue on both Slack connector and RabbitMQ connector, is it the same on other connectors? |
Fixes #4419 .
Modifications