diff --git a/docs/jvm-parameters-matrix-table.md b/docs/jvm-parameters-matrix-table.md index 90a32f0a..846e5dec 100644 --- a/docs/jvm-parameters-matrix-table.md +++ b/docs/jvm-parameters-matrix-table.md @@ -1,5 +1,5 @@ | **JVM Parameter** | **Enable?** | **References / Details** | -| --- | --- | --- | +| :--- | :--- | :--- | | -XX:+UseG1GC | Enabled by default in Java 8u191+ | Most important defaults specific to G1 and their default values.
https://dzone.com/articles/choosing-the-right-gc
https://wiki.openjdk.java.net/display/HotSpot/G1GC+Feedback
Alternative: Shenandoah GC | | -XX:+UseShenandoahGC | Alternative to G1GC. | Shenandoah Garbage Collector: experimental in Java 8, newer than G1GC, available in some OpenJDK 8 and newer releases.
https://wiki.openjdk.java.net/display/shenandoah/Main
https://dzone.com/articles/7-jvm-arguments-of-highly-effective-applications-1 | | -XX:+UseZGC | Yes (JDK 11+) | Z GC : Better Garbage Collector Algorithm than G1 or Shenandoah. JDK 11+ required.
The Z Garbage Collector, also known as ZGC, is a scalable low latency garbage collector designed to meet the following goals:
· Pause times do not exceed 10ms (*)
· Pause times do not increase with the heap or live-set size
· Handle heaps ranging from a 8MB to 16TB in size
At a glance, ZGC is:
· Concurrent
· Region-based
· Compacting
· NUMA-aware
· Using colored pointers
· Using load barriers
At its core, ZGC is a concurrent garbage collector, meaning all heavy lifting work is done while Java threads continue to execute. This greatly limits the impact garbage collection will have on your application's response time.
7 JVM Arguments of Highly Effective Applications
https://wiki.openjdk.java.net/display/zgc/Main | diff --git a/docs/matrix-table.md b/docs/matrix-table.md index 29c33563..369de279 100644 --- a/docs/matrix-table.md +++ b/docs/matrix-table.md @@ -1,7 +1,7 @@ # Kubernetes solutions or installers matrix table | PaaS Candidate | Role | Ecosystem | Infra Provider | On-Premise | Licence | HA | Standalone | Runs in Docker | Ingress + Storage
included | Automated
Deployment | Details | URL | -| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | +| :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | | kubeadm | SRE / DevOps | Kubernetes Upstream | Multi platform | Yes | OSS | Yes | No | No | No | No | Official kubernetes deployment tool | https://github.com/kubernetes/kubeadm | | Ansible Role with kubeadm | SRE / DevOps | Kubernetes Upstream | Virtual Machine | Yes | OSS | Yes | Yes | No | Yes (storage?) | No | Ansible role for kubeadm automation | https://github.com/geerlingguy/ansible-role-kubernetes | | kops | SRE / DevOps | Kubernetes Upstream | AWS | No | OSS | Yes | No | No | Yes | Yes | AWS compliant, alpha release
for other providers | https://github.com/kubernetes/kops | diff --git a/docs/message-queue.md b/docs/message-queue.md index a813ea2d..a02a1dc1 100644 --- a/docs/message-queue.md +++ b/docs/message-queue.md @@ -79,7 +79,7 @@ [![AMQ in a nutshell](images/AMQ.png)](https://developers.redhat.com/products/amq/overview) Product|Also Known As|Components|URL -:------|:----|:--------:|----: +:------|:----|:--------|:---- Red Hat AMQ 6|JBoss AMQ 6|Apache ActiveMQ|[Ref](https://access.redhat.com/documentation/en-us/red_hat_amq/6.3/) Red Hat AMQ 7|JBoss AMQ 7 (Broker) or Red Hat AMQ 7 Suite|AMQ Broker + AMQ Streams|[Ref](https://access.redhat.com/documentation/en-us/red_hat_amq/6.3/) Red Hat AMQ 7|JBoss AMQ 7 (Broker) or Red Hat AMQ 7 Suite|JBoss AMQ 7 (Broker) + Apache Kafka|[Ref](https://access.redhat.com/documentation/en-us/red_hat_amq/6.3/) diff --git a/docs/monitoring.md b/docs/monitoring.md index a6f1bb22..ba3c8efc 100644 --- a/docs/monitoring.md +++ b/docs/monitoring.md @@ -56,7 +56,7 @@ OpenShift Container Platform Monitoring ships with a Prometheus instance for cluster monitoring and a central Alertmanager cluster. In addition to Prometheus and Alertmanager, OpenShift Container Platform Monitoring also includes a [Grafana](https://grafana.com/) instance as well as pre-built dashboards for cluster monitoring troubleshooting. **The Grafana instance that is provided with the monitoring stack, along with its dashboards, is read-only.** | Monitoring Component | Release | URL | -| :----------------------- | :-----------------: | -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | +| :----------------------- | :----------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ElasticSearch | 5 | [OpenShift 3.11 Metrics & Logging](https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html#ocp-311-metrics-and-logging) | | Fluentd | 0.12 | [OpenShift 3.11 Metrics & Logging](https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html#ocp-311-metrics-and-logging) | | Kibana | 5.6.13 | [kibana 5.6.13](https://www.elastic.co/guide/en/kibana/5.6/introduction.html) | @@ -99,7 +99,7 @@ OpenShift Cluster Monitoring components cannot be extended since they are read o [Monitor your own services (technology preview)](https://docs.openshift.com/container-platform/4.3/release_notes/ocp-4-3-release-notes.html): The existing monitoring stack can be extended so you can configure monitoring for your own Services. | Monitoring Component | Deployed By Default | OCP 4.1 | OCP 4.2 | OCP 4.3 | OCP 4.4 | -| :----------------------- | :-----------------: | :------: | :-----: | :-----: | ------: | +| :----------------------- | :-----------------: | :------ | :----- | :----- | :----- | | ElasticSearch | No | 5.6.13.6 | | | | | Fluentd | No | 0.12.43 | | | | | Kibana | No | 5.6.13 | | | | @@ -280,7 +280,7 @@ Although it's exciting to see attempts to address the challenges of running Prom * [Prometheus Monitoring With Grafana. Prometheus Stats Dashboard and Prometheus Benchmark Dashboard](https://dzone.com/articles/prometheus-monitoring-with-grafana). How you construct your Prometheus monitoring dashboard involves trial and error. Grafana makes this exploration very easy and Prometheus has good built-in functionality. Monitored Component|Collector|Dashboard Number|URL -:------------------|:-------:|:---------------:|------------: +:------------------|:-------|:---------------|------------ ActiveMQ 5.x "classic"|[Telegraf](https://www.influxdata.com/time-series-platform/telegraf/)|[10702](https://grafana.com/grafana/dashboards/10702)|[Ref1](https://docs.wavefront.com/activemq.html), [Ref2](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/activemq), [Ref3](https://github.com/prometheus/jmx_exporter/blob/master/example_configs/activemq.yml), [Ref4](https://stackoverflow.com/questions/57107282/prometheus-and-activemq-integration) ActiveMQ Artemis/Red Hat AMQ Broker|[JMX Exporter](https://github.com/prometheus/jmx_exporter)|[9087](https://grafana.com/grafana/dashboards/9087)|[Ref1](https://github.com/prometheus/jmx_exporter/blob/master/example_configs/artemis-2.yml), [Ref2](http://techiekhannotes.blogspot.com/2018/12/artemis-monitoring-with-grafana.html), [Ref3](https://github.com/rh-messaging/artemis-prometheus-metrics-plugin) Message Streams like Kafka/Red Hat AMQ Streams|Other|[9777](https://grafana.com/grafana/dashboards/9777)| @@ -644,8 +644,10 @@ drwxrwxr-x 3 activemq activemq 19 Jan 10 16:22 .. * We can now see metrics displayed on Grafana and Artemis Dashboard: +JMeter|Artemis Grafana|Artemis Dashboard +:-------:|:---------:|:-------: ![jmeter artemis](images/jmeter_artemis.png)|![artemis grafana](images/artemis_grafana.png)|![artemis dashboard monitoring](images/artemis_dashboard_mon.png) -:-------|:---------:|-------: + @@ -721,7 +723,7 @@ drwxrwxr-x 3 activemq activemq 19 Jan 10 16:22 .. ## Message Queue Monitoring Messaging Solution|Monitoring Solution|URL -:-------|:-------:|-----: +:-------|:-------|:----- ActiveMQ 5.8.0+|[Dynatrace](https://www.dynatrace.com)|[ref](https://www.dynatrace.com/support/help/technology-support/application-software/other-technologies/supported-out-of-the-box/activemq/) ActiveMQ Artemis|[Micrometer Collector](https://micrometer.io/) + Prometheus|[ref1](http://activemq.apache.org/components/artemis/documentation/latest/metrics.html), [ref2](https://micrometer.io/docs/registry/prometheus) IBM MQ|[IBM MQ](https://github.com/ibm-messaging) Exporter for Prometheus|[ref](https://github.com/ibm-messaging/mq-metric-samples/tree/master/cmd/mq_prometheus) diff --git a/docs/openshift.md b/docs/openshift.md index 93df129b..fec23db9 100644 --- a/docs/openshift.md +++ b/docs/openshift.md @@ -80,7 +80,7 @@ * [Red Hat's approach to Kubernetes 🌟](https://www.redhat.com/en/topics/containers/kubernetes-approach) Reference | Author | URL -:---------|:-------------:|-------------: +:---------|:-------------|:------------- "Given the difficulty of navigating the cloud-native ecosystem, especially the one around Kubernetes, **there is a high demand for easy-to-administer development platforms** that deliver applications in Kubernetes-managed containers."| OMDIA|[Red Hat's approach to Kubernetes](https://www.redhat.com/en/topics/containers/kubernetes-approach) Industry momentum has aligned behind Kubernetes as the orchestration platform for Linux® containers. Choosing Kubernetes means you’ll be running the de facto standard regardless of which cloud environments and providers are in your future.|CNCF Survey 2019|[Red Hat's approach to Kubernetes](https://www.redhat.com/en/topics/containers/kubernetes-approach) “It's not just enough to do Kubernetes. You do need to do CI/CD. You need to use alerting. You need to understand how the security model of the cloud and your applications interplay.”|Clayton Coleman,Senior Distinguished Engineer, Red Hat|[Red Hat's approach to Kubernetes](https://www.redhat.com/en/topics/containers/kubernetes-approach)