For our hackathon project, we have considered three data sources
- Reddit hot posts by subreddit
- Twitter most recent posts in a specified timeframe by list of hashtags
- Google playstore reviews for application.
We publish this data to a centralized where we run the clustering and insight generation software We periodically generate tickets, that are ingested by a snapin with a command and a ticket is created on the devrev platform with the typescript sdk
We have considered the following snap ins
- playstore_snap_in
- reddit_snap_in
- twitter_snap_in
- ticket_creator_snap_in
- other_tweets_snap_in
Each snap in used the following secrets
- awsAccessKey - Access Key for AWS IAM User
- awsSecretKey - Secret Key for AWS IAM User
- regionName - Region Name for aws account
Each snap in has the following default inputs
- default owner id
- default part id
- app_name - For the multi app system, this is the app name the client want to register. Not that this app name must be the same as the one registered on the dashboard
This snap in runs on a 5 minute timer and fetches the most recent reviews for an app on the playstore It then forwards it for processing
- app_id - App id of the application on the play store
- queue_url - SQS queue to pusblish events
This snap in runs on a 10 minute timer and fetches hot posts for a subreddit on reddit It then forwards it for processing
- subreddit - Subreddit to monitor for hot posts
- queue_url - SQS queue to publish events
- reddit client id
- reddit client secret
These are used to access the reddit api
This snap in runs on a 5 minute timer and fetches newest tweets on twitter It then forwards it for processing
- myhashtags - Comma separated list of hashtags - eg #Gpay,#googlepay
- queue_url - SQS queue to publish events
- rapid_api_key - Api key for accessing the Rapid Api twitter api
This snap in defined a command that fetches already generated tickets from the data ingested by the other snap ins
- ticketUrl - Url for the sqs queue where the events are generated
/create-tickets :Count Count is the maximum number of tickets to create By default count is set to 1
This snap in fetches tweets based on a list of hashtags and exclusively finds feature requests. The idea is to monitor tweets for organizations within a common space like Google/Apple/Amazon pay, PhonePe. BharatPe etc for the payment and upi space This snap in uses fireworks llm library to classify the text. Tickets are then created on the Devrev Platform, the data is also published to a message queue so it can be consumed by our dashboard.
- queue_url - Message queue to publish the messages
- fireworks_api_key - Api key for accessing fireworks llm models
- google_api_key - Api key for accessing google translate api
- rapid_api_key - Api key for accessing the Rapid Api twitter api
/other_features :Count Count is the maximum number of tickets to create