This page explains how you can retrieve the credentials and keys to interact with Kensu.
Kensu includes two APIs, with separate credentials for each:
- The Ingestion API sends metadata to Kensu. Kensu agents wrap this API in order to send events. This requires an ingestion-token.
- The Expectation API lets you retrieve data from the Kensu server and create data checking rules from code. It requires an API token (Personal Access Token) for identification.
Kensu uses oAuth2 for dashboard and API authentication.
Kensu has SAML federation with Google. So you need a Google account.
If you don't use Google, that is not a problem. Just make up a Google email, as you only need it for this purpose.
Login to the Kensu dashboard
Log into the Kensu dashboard. Check the checkbox (a) to accept the Terms and Conditions then click on Sign in/up (b).
Click on Continue with Google and log in with a Google or GSuite account.
Getting the ingestion API token
Step 1: Click Preferences on the dropdown menu at the top right corner of the screen.
Step 2: On the Ingestion tab, click Copy to copy your authentication token. You will need to paste it into the conf.ini and other configuration files, as explained in these tutorials.
Getting the ingestion API URL
The URL can be copied from the same Ingestion tab. Click Copy to retrieve the URL.
Getting the expectation API PAT
Step 1: Access the External Application tab
Step 2: Click Copy to copy your PAT. This particular token is used to retrieve data from Kensu in order to consume them in the application (i.e., to add a rule, to display charts, ...)