Skip to content

Latest commit

 

History

History
29 lines (26 loc) · 1.8 KB

README.md

File metadata and controls

29 lines (26 loc) · 1.8 KB

botometer-checker-azure

A dockerized application that reads tweet objects from an Azure Event Hub, uses the Botometer API to check the account that posted each tweet for the probability to demonstrate a bot-like behavior and stores the result in a Cosmos DB container.

Setting environment variables

Twitter authorization: API (consumer) key, secret and access token, secret for the twitter app that will be used to make requests to the botometer API:

  • CONSUMER_KEY
  • CONSUMER_SECRET
  • ACCESS_KEY
  • ACCESS_SECRET

URL, Primary Key, and database name for the Cosmos DB database that is used to store the botometer results and the daily botometer API calls:

  • COSMOSDB_URL
  • COSMOSDB_KEY
  • COSMOSDB_DB_NAME

Azure Blob storage credentials: Connection string and blob container name which is used to store checkpoints while processing events the from Azure Event Hub (see also here):

  • STORAGE_CONNECTION_STRING
  • BLOB_CONTAINER_NAME

Event Hub credentials: Connection string, event hub name and consumer group which are used to read tweets from:

  • EVENTHUB_CONNECTION_STRING
  • EVENTHUB_NAME
  • EVENTHUB_CONSUMER_GROUP

Cosmos DB container names: For Botometer index which stores the botometer results for checked users and Botometer daily counter which stores the number of API calls made for a given day:

  • COSMOSDB_BOTOMETER_INDEX_CONTAINER_NAME
  • COSMOSDB_BOTOMETER_COUNTER_CONTAINER_NAME

Rapidapi key: Set the personal RAPIDAPI key obtained from https://rapidapi.com.

  • RAPIDAPI_KEY

Botometer session limit: Set the max number of Botometer API requests to be made in a single session.

  • BOTOMETER_SESSION_LIMIT