Is there any google chat module to send alerts via sensu's google chat handler to more than one room (chat room)?
Ex: As like in Slack we have multi-slack-handler.rb handler is there to trigger alerts on multiple channels via subscriptions which we defined./
Is this same kind of thing Possible with google chat??
In my case, I have created two channels in Sensu (sensu-core open source edition) but I am getting alerts in only one channel after few minutes I am getting alerts on another channel as well but it sends alerts in only one channel at a time. How can we get alerts in all the channels on sensu with google hangout handler?
I think you should check this module: https://github.com/anandtripathi5/google-chat-handler. It is a simple handler which you can add to your logger and configure the level of chat as required. Adding it multiple times with different Gchat room webhooks will push logs to multiple Gchat rooms simultaneously.
Related
I have a chat app and I am stuck while initiating the chat. According to pubnub, anytime I message to a new channel "A", that channel is created. My problem is that I want to subscribe to that channel and show the message but I cannot subscribe before the channel is created.
"Creating" PubNub Channels
Channels are not really "created", channels are just string tokens for routing messages. So there is no notion of creating a channel in PubNub (not officially, anyway).
The phrase "create a channel" is more of a concept than a real thing in PubNub. Within your app, creating a channel (a chat room) is a real thing. So you can subscribe to a channel that hasn't yet been "created".
So when your app "creates" a channel (starts a new chat room), your participating clients can subscribe to the channel and messages can be published later.
Or, clients can subscribe after messages are published and use fetchMessages to get any messages that were sent before the client subscribed.
I've built an ionic app that uses Ionic Cloud services to subscribe to FCM Push notifications. Currently, I receive the notifications whenever it's sent.
It requires 'CloudSettings' const to be configured in the app-module.ts, where the Push configurations like sender-id, android and ios specific configuration including GCM topics could be provided.
Now, I want to subscribe to additional topics based on the user selection. How to subscribe to different topics (dynamically) with Ionic 2 Cloud Services?
As 'CloudSettings' is a constant and imported in the app module, it could not be overridden. Is there any way to override the configuration?
I tried to reset the value for push.PushOptions before registering to, but it's not working. Any solution to this would be appreciated.
You can use something like azure notificaton hubs. They allow multiple tagging and registration for single devices.
Create a backend app to manage sending and subscriptions and register via this instead of the ionic backend.
There are lots of tutorials to support this, but ultimately once the push registration was completed and the FCM token returned,I manually registered this via my .NET backend where I can control the tags and allow them to be easily updated depending on user preferences. The backend app can then be used to broadcast notifications depending on the tags you want to receive them
I'm very new to xmpp and jabber services.
I try to add voting ability to jabber chat rooms. What is the best way to do it?
I know, there are some bots written for jabber.
I have openfire server. I think, bot can be added to every chat room, created on server, but what is the way to store voting results, for example.
Case:
Chat room is created
Users are added
Bot is added to room
Bot reads messages and when it gets
/voting firtree:'FirTree decoration' 1:'red balls' 2:'green balls'
Voting is created
User sends
'/vote firtree:1'
and his vote goes to 1st variant of firtree voting.
First from this question :
Asmack/openfire How do I keep a user permanently in groupchat room
I read that I cannot use MUC to keep the user persistent in the group, they'll automatically leave the group and can rejoin after they come online again, that concept is like IRC like what've been asked in here -> http://community.igniterealtime.org/thread/48020.
Then from the stackoverflow question I read about using pubsub, then I've done some research about pubsub and what I've got is pubsub can persist the user to be in the group even the user is offline but the message flow is more like one directional from the publisher to the subscriber (read-only).
So if I want to create a group chat application can I use pubsub and set all the member to become both publisher and subscriber? or is there any alternative solution?or my understanding of the pubsub and MUC is incorrect?
my goal is to create some group chat like in the whatsapp or blackberry messenger group.
Thanks.
You can make users permanent in Group chat in MUC by changing the following code of openfire.
File : src/java/org/jivesoftware/openfire/muc/spi/LocalMUCUser.java
change line 547-550:
// TODO Consider that different nodes can be creating and processing this presence at the same time (when
remote node went down)
removeRole(group);
role.getChatRoom().leaveRoom(role);
TO:
// TODO Consider that different nodes can be creating and processing this presence at the same time (when
remote node went down)
// TODO Dont remove user from group when they go offline.
//removeRole(group);
//role.getChatRoom().leaveRoom(role);
I want to integrate my web application with chat and notification service and the foremost and the best, i understand is XMPP. After going through the nitty gritties, though i understood most of it but I got stuck here i.e. how will i run a Chat and notification service together.
One option is to have run different connections of Strophe, long polling with different accounts one for chat and other for notifications.
Other one is to have both notifications and chat on the same accounts but now the problem if the user signs out from chat he wont be able to receive notifications.
The first option does not seem feasible to me, but is there a way the later one could work?
Use one connection, to your "chat" service. Run your notification service as a component on your chat server, or run a separate server and federate them together. The client will be able to contact the notification service (and vice-versa) via the naming scheme in the Jabber ID's (JIDs) that you pick. Make sure you pick a different domain name for the user accounts on the chat side than for the notification service.