track API usage #1677
Merged
track API usage #1677
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jrjohnson
requested changes
Nov 18, 2016
| @@ -47,3 +47,5 @@ parameters: | |||
| cas_authentication_version: 3 | |||
| cas_authentication_verify_ssl: true | |||
| cas_authentication_certificate_path: null | |||
| enable_api_tracking: false | |||
There was a problem hiding this comment.
So we can use this same parameter on the frontend lets call it just enable_tracking.
jrjohnson
approved these changes
Nov 22, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #1148
the "tracking enabled" flag and the tracking code itself are exposed via the config endpoint in the API (the latter only if the tracking has been enabled.)
google will receive the following three data attributes for each API controller hit