I have Eventbridge (EB) schema discovery working. However, I need a way to be alerted to a new schema being detected.
My potential solution:
Use the boto3 api for schemas, and keep polling the endpoint to check for new versions.
Is there a better way to do this? I have not seen anything in the documentation about an event that I might be able to subscribe to from EB to get notified when a new version is detected.
I have tried looking at the EB documentation and searching for solutions but have come up short.
Cheers team, appreciate your time in reading this.
Related
I am using Revulytics SDK to track feature usage and came across the below problem.
I am sending feature usage after properly setting up the SDK configuration etc, using the EventTrack() method like this:
GenericReturn grTest = telemetryObj.EventTrack("FeatureUsage", textBoxName.Text.ToString(), null, false);
This returns OK and usually, I can see the usage data in the dashboard. However, after multiple tests, the data I am sending does not show up on the dashboard.
Can anyone hint me how to debug this? Thanks for any help!
I hit a similar issue when first working with this SDK.
I was able to address this as soon as I understood the following:
There are event quotas for the incoming events;
Event names are used for making the distinction.
So when I was sending dummy test data, it made it there, but when I sent some demo data for stakeholders, it was not showing up.
I think the same happens here. You're getting the event name form textbox.text... Pretty sure that varies every time you run the code.
Here are the things to keep in mind when testing your code:
the server has a mechanism to discard / consider events;
implicitly, it allows first xx events depending on the quota;
if you are sending more than xx events, they will not show up in reports.
So, you must control which events to discard and which to consider (there are a couple of levels you can configure, and based of them you can get the events in various types of reports).
Find the "Tracked Events Whitelist Management". You will be able to control these things form there.
This blog helped me (it is not SDK documentation): https://www.revulytics.com/blog/getting-started-with-usage-intelligence-part2-event-tracking
Good luck!
new to ruby and ruby on rails here.
Have database which gets all articles from API and saves it. This works by find or create, however this way it never deletes articles. It only gets the current articles and new articles, but no webhook to tell me if an article is removed. How can I do this without a web hook to tell me if an article has been removed? Purging database every day is not an option because of other data linked.
I can't seem to find anything without the use of webhooks. Any one ideas?
If you have no Webhook to tell you the article removed-status. You only have two ways to remove the old-article.
Use polling to query the API to check the article removed-status. If the article has removed been checked by your polling, you can remove the old-article.
Set a time-base, for example : seven days, then if the article created in your database over seven days, you seem the article to a old-article, and you remove the old-article.
The disadvantage of 1.way make more system cost.
The disadvantage of 2.way is inaccurate.
All the ways aren't perfect, but if you have no Webhook, this is only two ways that you can do.
I've been looking for a way to have a user acknowledge a
ticket after it has been assigned to them. I don't know if
this is a built in feature or if there is a plugin that
will create a state/button for a user to accept a ticket
after it has been put in there queue. I would expect to
see something like this from the ticket window around
workflow or start progress but no amounts of digging
through configuration settings has turned anything
relevant up.
Does anyone know about this added functionality in JIRA?
Much thanks.
I did this by a custom workflow step. After an issue arrived to an assignee (with status New) he/she should move it to another step (with status Open). Until he/she does it, the issue is considered as not noticed/reached the assignee. Also I have had a report showing issues with New status for more than a predefined period of time.
I'm not aware of a ready-made plugin which performs similar task (perhaps, I should dig into my posts on Atlassian answers to discover some clues for other solutions).
As #Stan says above, a custom workflow is the way to implement this. The workflow functionality in JIRA is very flexible and as a result has a bit of a learning curve, but Atlassian's documentation is pretty good. Post back here if you need help.
I am in need of replicating all kayako helpdesk tickets into TFS. This includes creation of the ticket, updates of the ticket, and closure of the ticket. I've looked around and I can't seem to find any elegant solution to this. Can any of you point me int he right direction?
You can roll your own integration by building on the TFS Integration Platform.
Does Kayako support webhooks? webhooks allow you to send data when it happens, so for example when a ticket is created or when it is resolved - you can then have your application process that data. This is far better than having to make repeated calls to an API to see if there are changes to a system.
What is the simplest way how to check if user is online and display list of online users?
The only way I can think of is some periodic polling server to update last action timestamp, and when last timestamp is more than xx ago, user is considered to be offline. But it doesn't seem like too eficient solution.
Authlogic can do this by default, and is a great authentication system that is very powerful. I would suggest migrating your current authentication system over to it (maybe a days worth of work, depending how customized your system is).
If you can't (or simply don't want to) move your application over to Authlogic, you can check out the source code at the link above, as well as an example project here.
You could potentially check the session time, if you use database session store. When the updated_at extends past a certain time, assume the user is no longer active. This could be problematic as well, however.
Being honest, it's a somewhat difficult scenario to tell the active number of users without some form of periodic server polling. Your thought is not a bad one.
We can list the online users using active record session store, please see this github app https://github.com/mohanraj-ramanujam/online-users