Update documentation and samples for Event Streams Lite and Standard

[bmpotter]

I think what we have been using in the public cloud is what is now called Event Streams Classic. Figure out if we need to do anything different to use our samples with Lite and Standard.

See some discussion about this in the edge-fabric-users slack channel on 9/5/19

[t-fine]

Joe Pearson - "I know that Classic works." John Walicki - "Aha - it works! ... I'm using a Event Streams (Lite) service instance."

https://cloud.ibm.com/docs/services/EventStreams?topic=eventstreams-plan_choose

Lite: Kafka 2.2 The Lite plan is free for users who want to try out Event Streams or build a proof-of-concept. We do not recommend the Lite plan for production use. The Lite plan offers shared access to a multi-tenant Event Streams cluster.

• Try our fully managed Apache Kafka offering free of charge
• The Lite plan offers access to a single partition in a multi-tenant Event Streams cluster.
• Lite plan services are deleted after 30 days of inactivity.

Standard: Kafka 2.2 The Standard plan is appropriate if you require event ingest and distribution capabilities but do not require any additional benefits of the Enterprise plan. The Standard plan offers shared access to a multi-tenant Event Streams cluster.

• Pay as you go access to the multi-tenant Event Streams service.
• Charged on a per instance-hour basis. An instance-hour refers to an Event Streams partition.
• Charged on a per GB basis for outbound data consumption.
• If you are looking for our Lite Plan, please change your region to Dallas.

Classic: Kafka 1.1 The Classic plan gives access to the previous edition of the Standard plan and is provided for existing workloads and backward compatibility only. You should provision new workloads against the Standard plan. The Classic plan is appropriate if you require event ingest and distribution capabilities but do not require any additional benefits of the Enterprise plan. The Classic plan offers shared access to a multi-tenant Event Streams cluster.

• Pay as you go access to the multi tenant Event Streams Classic service.
• Charged on a per month basis (pro-rated) per partition.
• Changed on by number of messages sent or received per month.
• Multi-Tiered

[t-fine]

Hi Team, for newly created instances (standard plan) of Event Streams, are Kibana/Grafana not available anymore? What about the Classic plan?

for standard/enterprise plan, Kibana is replaced by LogDNA, so if you create an instance of ActivityTracker with LogDNA, you will find your topic create/delete events there. Grafana will be replaced by Sysdig, but this feature is not ready yet. for Classic plan, they are working as it is, but Classic plan is deprecated on Jan.2020, and Kibana is sunset on Sept.2019, Grafana date is not determined, but sometime around 1Q 2020 if Sysdig feature goes well.

Article about migrating from the classic plan to the standard plan: https://cloud.ibm.com/docs/services/EventStreams?topic=eventstreams-migrate_classic_plan

https://www.ibm.com/cloud/blog/announcements/ibm-event-streams-releases-a-new-and-enhanced-standard-plan "As a result, we will be renaming any existing Standard plan deployments to be named "Classic." This will not impact the stability of your applications."

[t-fine]

After some additional research I believe that this change can be made without any changes to the KC docs. Since the code remains the same, in addition to topic names, and the only choice from here forward will be to provision a "Standard" (or Lite) plan, as the Classic plan will no longer be offered or supported.

I will do some experimentation once I change our public cloud event streams plan for examples to standard, and if all works as is I will close the issue.

[t-fine]

https://www-03preprod.ibm.com/support/knowledgecenter/SSFKVV_3.2.1/devices/installing/cpu_load_example.html

under Deploying an instance of IBM Event Streams in step 8. You can either create credentials...:

can you remove the slashes in the two export commands so they look as follows

`export EVTSTREAMS_API_KEY` (the value of api_key)
`export EVTSTREAMS_BROKER_URL` (all kafka_brokers_sasl values in a single string, separated by commas)

and finally, right beneath that is "For example, from the view credentials pane:" could you change that long export EVTSTREAMS_BROKER_URL=... to the following: export EVTSTREAMS_BROKER_URL=broker-4-x7ztkttrm44911kc.kafka.svc01.us-south.eventstreams.cloud.ibm.com:9093,broker-3-x7ztkttrm44911kc.kafka.svc01.us-south.eventstreams.cloud.ibm.com:9093,broker-2-x7ztkttrm44911kc.kafka.svc01.us-south.eventstreams.cloud.ibm.com:9093,broker-0-x7ztkttrm44911kc.kafka.svc01.us-south.eventstreams.cloud.ibm.com:9093,broker-1-x7ztkttrm44911kc.kafka.svc01.us-south.eventstreams.cloud.ibm.com:9093,broker-5-x7ztkttrm44911kc.kafka.svc01.us-south.eventstreams.cloud.ibm.com:9093