You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info
On Wednesday, October 10, 2018, we began releasing a new cloud version of Apigee Edge for Public Cloud.
New features and enhancements
This section describes the new features and enhancements in this release.
General availability of API Monitoring
Apigee API Monitoring helps operations teams increase API availability for application developers, customers, and partners. Apigee API Monitoring works in conjunction with Apigee Edge Cloud to provide real-time contextual insights into API performance, helps quickly diagnose issues, and facilitates remedial actions for business continuity. For more about API Monitoring, see Introduction to API Monitoring.
On Thursday, October 25, we added support for the Latency dashboard. The Latency dashboard displays latency information for the API proxies and target services in your organization. You can investigate latency metrics for a one hour window at any time in the past 30 days.
On Monday, October 29, we added support for two built-in roles, API Monitoring Administrator and API Monitoring User, that define the permissions required to access API monitoring only. See Access API monitoring for more.
General availability of the Hosted Targets feature
With Hosted Targets, you can host your Node.js APIs on Apigee Edge. Hosted Targets lets you deploy Node.js applications in a native, secure, scalable, and isolated environment where Edge API proxies can call them as target services. For more about Hosted Targets, see Hosted Targets overview.
General availability of the Extensions feature
With the Extensions feature, developers can build API proxies that consume a cloud service or SaaS application. The feature includes extensions for Google Cloud Firestore, Google Cloud Pub/Sub, Google Cloud Storage, and others. Extensions abstract away the complexity represented by considerations for security, data formats, request/response transformation, and wire protocols in interacting with external systems. For more about Extensions, see What are extensions?
The following bug is fixed in this release. This list is primarily for users checking to see if their support tickets have been fixed. It's not designed to provide detailed information for all users.
|List API monitoring roles as built-in rather than custom roles
The following roles related to API Monitoring are now listed as built-in roles, rather than custom roles: API Monitoring Admin and API Monitoring User
|Uploading JAR files to shared flow fails
If you upload multiple JAR files to shared flow and the combined total size is greater than 15MB, then you will receive an error. In addition, when deleting a resource, you will need to save the change to a new revision; you will be prevented from saving to the current revision.
This release has the following known issues.
|API monitoring roles are not set
The following roles are available as built-in roles, but are not currently set: API Monitoring Administrator and API Monitoring User. Do not configure users to use these roles.