Show Table of Contents Hide Table of Contents English English Multi-page HTML Single-page HTML PDF ePub Product1. API analytics1.1. Prerequisites1.2. Determine the metrics and methods you want to track1.3. Create your metrics and methods1.4. Set up reporting1.5. Check that traffic is reported correctly1.6. Troubleshooting1.7. Controlling who sees the analytics1.8. Asynchronous and batch traffic reporting1.9. Accessing analytics data by API and email reports2. API Versioning2.1. Goal2.2. Prerequisites2.3. URL versioning2.4. Endpoint versioning2.5. Custom header versioning3. Getting Started3.1. Prerequisites3.2. Connecting Echo API to 3scale3.2.1. Step 1: Define your API and create your first API key3.2.2. Step 2: Integrate via API gateway in the staging environment3.2.3. Step 3: Capture traffic for specific methods3.3. Congratulations!3.4. What’s next?3.5. Closing the loop3.6. Help4. Zero To Hero Developer Portal4.1. Goal4.2. Prerequisites4.3. Step 1: Plan your portal concept4.4. Step 2: Set up your CMS editing environment4.5. Step 3: Define page layout templates4.6. Step 4: Create your page hierarchy4.7. Step 5: Edit your page headers4.8. Step 6: Populate images and other assets into the CMS4.9. Step 7: Fully customize your branding with CSS4.10. Step 8: Go liveLegal Notice Product Red Hat 3scale 2.2For Use with Red Hat 3scale 2.2Red Hat Customer Content Services Legal NoticeAbstract This guide documents product features for Red Hat 3scale 2.2. 1. API analytics Where did the comment section go?Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.