Avoiding Common Mistakes

In this guide we'll cover some of the common mistakes we see people make when they first start to use PYLON.

To help explain concepts our examples will star Dave a fictitious developer who works at the equally fictitious social technology agency 'Perfect Curve'.

Common misunderstandings

Interaction limits

A single recording cannot exceed 1 million interactions per day under any circumstances.

Dave checked his contract with DataSift; it says he can record and analyze 12 million interactions per month. Dave is interested in an event which happens tonight and decides to use his full allowance of 12 million interactions in one night.

Dave’s recording will stop when it reaches 1 million interactions.

API analyze limit

The /pylon/analyze rate limit is reported as a daily limit but is enforced every second.

Dave checked his contract with DataSift; it says he can make 20k calls to the /pylon/analyze endpoint every 24 hours. Dave wants to complete lots of analysis on a month of data in his recordings by the end of the day. He writes a program which will use the endpoint 2,000 times in 10 minutes.

Dave’s analysis results will not be returned as soon as he exceeds 0.23 calls a second.

Account versus identity API key

The API key shown on the landing page of app.datasift.com is the Account API Key. The Account Name and Account API Key are only used when creating and managing identities. It is not used for recordings or analysis.

Managing and analyzing recordings must be done as an identity. You should have an identity for your own recordings and each of your customers should have their own identity.

Identity credentials are the Account Name and the Identity API Key. Identities do have a label but this is not used as part of the credentials.

Dave has started a subscription with DataSift and has the following credentials.

Dave's company Perfect Curve
Account name perfectcurve
Account API key bd1e0205050d83d5c58894de8526c9

Dave creates an identity called “perfect_test” for Perfect Curve to use as a testing identity.

Credentials used by Dave to create the “perfect_test” identity Account Name
Account API Key
Credentials Perfect Curve use to manage and analyze recordings Account Name
“perfect_test” Identity API Key

Perfect Curve have a new customer called “Twenty Twelve”. Dave creates a new identity for the customer. All recordings and analysis for Twenty-Twelve will use the new identity credentials.

Credentials used by Dave to create the “twenty-twelve” identity Account Name
Account API Key
Identity Twenty-Twelve use to manage and analyze recordings Account Name
“twenty-twelve” Identity API Key

User interface versus API

The PYLON Web user interface (UI) at app.datasift.com does not provide the full functionality available when using the API. The UI cannot do the following:

  • Run nested analysis queries
  • Use time offsets for analysis queries
  • Analysis timestamps which are exclusive rather than inclusive
  • Access super public text samples

Starting a new recording with a previously used CSDL definition

From PYLON 1.7 onwards it is now possible to start a new recording when the interaction filter is exactly the same as an interaction filter used by an existing or previous recording. The new recording will be given a new unique id.