Imported Google Group message. Original thread at: Redirecting to Google Groups Import Date: 2016-01-19 21:03:34 +0000.
Sender:Brandon Lamb.
Date:Friday, 26 December 2014 18:55:23 UTC.
Good morning!
Hey I wanted to request screenshots of the UIs. Until I get tyk setup, and also go through installing mongo and whatnot, I’m not sure what this stuff looks like.
Better yet, a demo site, but 10-20 screenshots would be fine.
Imported Google Group message.
Sender:Martin Buhr.
Date:Friday, 26 December 2014 19:58:26 UTC.
Hi Brandon,
Here you go - these are of the current Dev version (pre-release) and not on an active system, which will be coming out shortly - the only real change is the additional import (Apiary) and upstream API latency data graph (blue line).
Dashboard page, this is the first page you see. You can filter by API (and version), or view aggregate data, this displays hits and error data in the exiting version and displays upstream latency data in the upcoming version:
User listing page - these are the users that have access to the dashboard, theses users are grouped by organisation (as are upstream API’s) so whole API’s and their management can be segregated by organisation:
User detail page: Here you can set up the user data or revoke their access, you can also change their assigned API key - the dashboard has a REST API (not publicly documented - this is still to be finalised).
API LIsting page - this is where the API Definitions are listed that are currently in the system and their status (active / inactive):
API Import form - if you are currently using the Tyk gateway without the dashboard (completely possible, the dashboard is mainly for analytics and simplified management), you can use this form to cut and paste your API definitions into the service, the API then becomes listed:
API Configuration detail page - here you can set up your API, it mimics all the settings that are available to a standard API Definition file:
Webhooks listing, all API’s can have webhooks attached to various system events, these can be shared across configurations:
The webhook details page:
The API Key list, these keys are currently active on the system and give access to various upstream API’s:
Key details page, here you can assign quotas, limits and API version access across upstream API’s:
The remaining pages in the system are all to display analytics data, by endpoint, by key and errors:
Each chart can be filtered and opitmised for a range and resolution.
That’s pretty much the whole dashboard, let me know if there’s anything else.
Cheers,
Martin
Imported Google Group message.
Sender:Brandon Lamb.
Date:Friday, 26 December 2014 19:58:26 UTC.
Hi Brandon,
Here you go - these are of the current Dev version (pre-release) and not on an active system, which will be coming out shortly - the only real change is the additional import (Apiary) and upstream API latency data graph (blue line).
Dashboard page, this is the first page you see. You can filter by API (and version), or view aggregate data, this displays hits and error data in the exiting version and displays upstream latency data in the upcoming version:
User listing page - these are the users that have access to the dashboard, theses users are grouped by organisation (as are upstream API’s) so whole API’s and their management can be segregated by organisation:
User detail page: Here you can set up the user data or revoke their access, you can also change their assigned API key - the dashboard has a REST API (not publicly documented - this is still to be finalised).
API LIsting page - this is where the API Definitions are listed that are currently in the system and their status (active / inactive):
API Import form - if you are currently using the Tyk gateway without the dashboard (completely possible, the dashboard is mainly for analytics and simplified management), you can use this form to cut and paste your API definitions into the service, the API then becomes listed:
API Configuration detail page - here you can set up your API, it mimics all the settings that are available to a standard API Definition file:
Webhooks listing, all API’s can have webhooks attached to various system events, these can be shared across configurations:
The webhook details page:
The API Key list, these keys are currently active on the system and give access to various upstream API’s:
Key details page, here you can assign quotas, limits and API version access across upstream API’s:
The remaining pages in the system are all to display analytics data, by endpoint, by key and errors:
Each chart can be filtered and opitmised for a range and resolution.
That’s pretty much the whole dashboard, let me know if there’s anything else.
Cheers,
Martin
Imported Google Group message.
Sender:Martin Buhr.
Date:Friday, 26 December 2014 20:19:33 UTC.
Outstanding, thank you!