Is their any event apart from bots to listen to channel deletion in teams.
So that I can perform some actions on channel deletion.
Currently I could see only bots can handle such events.
Bots are one way, but this should also be possible using the Graph - specifically there is a Change Notification capability, as per https://learn.microsoft.com/en-us/graph/teams-changenotifications-team-and-channel . Per this doc:
You can get notified whenever a team or channel is created, updated, or deleted.
Related
Hi I want to find out when the channel is created for polling purpose I want this data means depending on the creation time I can find out whether new channel is created in Microsoft Teams if yes which it is.I checked with the graph api but it doesn't gives me the information like creation time of channel.
Is there anyway to delete bulk of messages from the slack application in one go, without paying for any package?
I need to introduce a mechanism which will delete the messages filed in the slack after certain period of time and this mechanism will work after certain interval
There is no API method for bulk operations. You have to keep track of a list of messages and invoke chat.delete for each on your own (in the code of your Slack App).
I created an Azure Event Grid Topic and I can send events to it. How can I view the events submitted to that topic?
In the Azure Portal, I can view the Event Grid Topic and see the topic's metrics but I cannot find a way to view the event messages.
At the moment, I created a workaround where I send all messages to a storage queue. The issue with this, Azure Storage Explorer doesn't let me scroll through thousands of messages; it limits me to viewing a single page of 50 +/- records.
try to use the Azure Event Grid Tester. You can clone any event subscription to the local machine subscriber via Hybrid Connection and/or ngrok tunnel channel.
The following screen snippet shows this tester with 2079 events on the custom topic rk20180724topic2:
I have inherited from a colleague who left a system module that integrates with Exchange Online in Office 365. Essentially what this module does is interact with with the remote Exchange service via EWS Managed API; subscribe for push notifications on changes in a user's calendar.
Change events do get posted to our web service and that is fine. And based on the frequency parameter we defined, the status checks messages also get posted on expected intervals, as per description about the subscription keep-alive behaviour.
The problem is, in observation, the subscription does not perpetuate despite responding with SubscriptionStatusType.OK to keep it ongoing. We never send SubscriptionStatusType.Unsubscribe since there is no error condition found in notification in messages. It seems to only last 9 to 14 hours before the Exchange service stops sending any status checks or change notification messages. When we make subscriptions from two separate web servers (different notification callback URLs), their subscriptions seem to die out around the same time.
Haven't found any clues that would cause the Exchange service to cancel/expire our subscriptions. What other conditions might contribute to this premature unsubscribe?
Exchange will "lose" subscriptions on a fairly regular basis, especially in the O365 environment because mailboxes are continually being shuffled onto different servers in order to load balance the entire ecosystem. Even in an on-prem Exchange you can lose subscription if a CAS restarts. Unfortunately to build a reliable app, you have to check periodically that you heard from Exchange via some kind of notification or heartbeat.
Here is my use case: I am developing a trading application and i want to send incremental stock updates (bidQty etc) to active consumers instead of the whole quote and a snapshot update to a new consumer (to start with).
Now, is it possible to override any ActiveMQ's class (implementors of Topic) to achieve this behavior? Any clues on this would be helpful .
If the same is possible in any other openSource provider, please let me know.
This is NOT a case where you simply can change the implementation of topic. You should actually avoid changing the implementation of core ActiveMQ features to solve specific business requirements. Fixing bugs and adding core messaging features is another thing.
There are multiple ways to solve your use case with regular ActiveMQ features.
Separate Sync and Update channel
I would probably divide the "sync/snapshot" channel from the "incremental update" channel.
One way is to implement the "snapshot-sync" as JMS request/reply where the consumer asks the provider for a sync, then continues to rely on incremental updates pushed via the topic.
Advisory messages and Selectors
You can also implement it all using a single topic using a mix of AdvisoryMessages and JMS Selectors.
An idea (you can do this in many ways):
Introduce two message properties: MsgType and Receiver
Mark each incremental update with MsgType=inc
Mark each snapshot with some client id of the consumer, Receiver=.
Have the producer listen to advisory messages from ActiveMQ and and fire a snapshot/sync message marked with Receiver= and MsgType=snapshot when there is a new client subscribing the stock topic.
The client subscribes with a selector of something like
MsgType='inc' OR (MsgType='snapshot' AND Receiver=<me>)
This way you can trigger snapshot syncs with specific clients as well as incremental updates for all clients.
If you start think about the dynamics you already have, you can probably think of another ten or so solutions.
Retroactive Consumers
You might have some use of a Retroactive Consumer - the example actually shows a scenario similar to yours.