Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API Analytics Use Case #4178

Open
mattab opened this issue Sep 25, 2013 · 3 comments
Open

API Analytics Use Case #4178

mattab opened this issue Sep 25, 2013 · 3 comments
Labels
Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.

Comments

@mattab
Copy link
Member

mattab commented Sep 25, 2013

It would be fantastic and very relevant to use Piwik as a API Analytics service. Piwik with its powerful log analytics and import can provide great insights in monitoring API and web services, such as: API request counters, successful requests, requests with errors, API Performance measurement, Continuous API monitoring. Count how many users use the API, which users use it often, which parameters they use, etc.

We would like to think about this use case a bit more and document how to use Piwik as a API Analytics platform. We have ourselves two APIs we could track using Piwik as a start.

@mattab
Copy link
Member Author

mattab commented Sep 25, 2013

Random notes:

  • Set "Visit duration" to 1 day to have accurate "unique users" metric
  • Unique Visitors per custom variable value is very interesting
    • CVariable Unique Visitors metric might is missing for month
  • option to turn Page URLs parameters to Custom Variables? (makes API usage analysis easier)

@mattab
Copy link
Member Author

mattab commented May 28, 2014

See also #5257 Application Performance Management & Monitoring

@MoralCode
Copy link

Being able to monitor HTTP request methods (POST/PUT/PATCH/DELETE) would also be nice

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Projects
None yet
Development

No branches or pull requests

2 participants