It is not clear enough for API owner about how to add a dashboard for monitoring API Usage

[Nazarah]

Usability Issue

Two primary things API owner wants to do after adding his/her API is to provide API documentation and to set up analytics to monitor API usage. However, except for Quick tour, there is no clear enough information in API profile about how to start using analytics. User often has to start a quick tour to get this information. However, quick tour also doesn't describe clearly about adding analytics functionality.

Enhancement

• Decide whether to use the term "dashboard" or "Analytics" in all places in APInf [these terms are often misleading to users. Ours is actually an analytics which gives detailed graphs and information on API. On the contrary, Dashboard can be the home page displayed right after user signs in to give him briefs about important information alerts that s/he needs to consider]
• Having S-alert close to proxy bar to indicate user can add API analytics from this place. S-alert message should be informative. The alert can stay as long as user doesn't close it manually.

Consideration Similar strategy for API Documentation

Additional work

• Tutorial video about adding and using API analytics.

[Nazarah]

In Next, there is provisions to show instructions o how to use and API. However, we need to add a new issue for writing those in i18n files. closing this issue and opening a new one for that