URL: https://rol.redhat.com/rol/rhz/rhls/course/jb240ea-2.4/ch01s03
Reporter RHNID: christian773
Section: introduction-3scale - Overview of API and Red  Hat 3scale Benefits and Use Cases
Language: en-US (English)
Workaround:

Description: #JB240 Early Access feedback

• DATE: 2019.08.16
• WHO: Chris Ruettimann
• Company: uniQconsulting ag - Switzerland

• Web: https://www.bitbull.ch
• Git: https://github.com/joe-speedboat
• Email: chris@bitbull.ch (rh email gets created next days)

• Reason for contact: I have to teach JB240 7. October 2019 in Stuttgart (DE)

• Feedback url: https://cloud.bitbull.ch/s/zGL63rBTBpGDK6w
• If you need rw access, just tell me
• If site get blocked, tell me your IP, I will exclude in GeoIP blocking
• Classroom Helpers are mentioned to provide additional support if needed (not yet finished, but menu is close)

1. 1. General
      Hi RH team
      I'm Chris
      In early days (2001) of Red Hat I was an external trainer for Red Hat RHCE courses in Switzerland and Germany.
      Then I jumped into Enterprise customers business and saw a lot of good and bad things.
      This year I'm happy to join the crowd again and happy to see that 700 employees increased to 15'000
      Hope you are doing well and If I can help with review, just kick me.
      I will try to provide feedback as fast as possible.
      Sometimes my comments may look bit picky, just ignore then, I just try to point as clear as possible.

1. 1. overall results
      I'm probably way to early to review your work, sorry for that
      Just let me know if I can help with testing/reviewing
      thanks chris

1. 1. My two cents about the Early Access course
      Happy to see the JB240 gets cleaned up.
      (I have notes about unsolved issues in current JB240 if you need, but I am pretty sure you already know)
      Today I tested what's present, looks much nicer and for sure it will be easier for the students to jump into this topic.

• Section 3.
• Details about Metric creation are missing (section 3.2 probably not yet finished).
  Metric and Method must not use same name!?

• Section 1.2: Guided Exercise: Basic API Configuration
• Figure 1.6: Define the limits of your API
• Metric or method foo is not part of excercise, new screenshot needed
• Method gethello is mentioned

• Figure 1.5: Enter details for your new application plan
• New screenshot needed

• Figure 1.7: Create a new account
• New screenshot needed

• Figure 1.8: The account details screen
• New screenshot needed

• Figure 1.9: Create a new application for the account
• New screenshot needed

• Figure 1.10: Application keys
• New screenshot needed

• Section 9. Integrate the newly created API with the Backend API. Use the following configuration details
  Should be: Integrate the newly created Echo API with the Backend API. Use the following configuration details
  (Because there is a SS called "API" as well which must not be used and this may confuse students new to 3scale)

• Figure 1.11: Integration configuration
• New screenshot needed

• Section 10.2 Return to the Integration Configuration page, and reapply the changes.
• Request should call /hello instead of /gethello to match the gethello metric/method !?

• Section 11.2 + 11.3 Create Mapping Rules
• Suggestion: Use /hello instead of /gethello because method has name gethello which may be confusing students
• Create mapping rules before showing analytics page with the results (just reorder) so students will understand
• create mapping rules
• hit request
• see results in analytics