As you review your analytics, you may see an entity value of (not set) displayed, including the parenthesis, for your API Proxies, Product, Developer, Developer Apps and other dimensions. This may or may not be an issue.
(not set) means Apigee doesn't have enough information. For
example, developer apps are associated with developers, API products, and by extension API
proxies. When a developer app makes an API call with an API key or OAuth token, all those
associations are made in analytics. However, if an API proxy is open and doesn't require an API
key, Apigee has no way of knowing if there is a developer, developer app, or product associated
with the API call.
(not set) could mean doesn't apply. For example, the "Flow
Name on Error" dimension shows the named API proxy flows where errors occurred. In that case, all
non-error calls will be shown as
(not set) because there was no error in the
The following table summarizes possible explanations for why you are seeing (not set) on a particular dimensions.
|Dimension||Possible Meaning of "(not set)"|
|API Proxy||A call to an API proxy reached the Apigee routers, but was malformed, never reached the proxy, and the message processor returned a 404 status code with a classification error. This means that there are some callers that are making malformed calls.|
|API Product||Not all of your API proxies and developer apps are using products. For information about how to get your API proxies and developer apps to use products, see Managing API products.|
|Developer||Some of your traffic is being generated by unregistered developers. This traffic may originate with an internal-use or public API. For information about how to register your app developers, see Registering app developers.|
|Developer Apps||Some of your traffic is being generated by unregistered apps. This traffic may originate with an internal-use or public API. For information about how to register your developers' apps, see Registering apps and managing API keys.|