Update README

cefriel · Nov 13, 2020 · 63ea59b · 63ea59b
1 parent 3c56a6b
commit 63ea59b
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 1 deletion.
diff --git a/README.md b/README.md
@@ -60,6 +60,10 @@ Projects using Chimera:
 Publications:
 - `Scrocca M., Comerio M., Carenini A., Celino I. (2020) Turning Transport Data to Comply with EU Standards While Enabling a Multimodal Transport Knowledge Graph. In: The Semantic Web – ISWC 2020. Springer. https://doi.org/10.1007/978-3-030-62466-8_26`
 
+### Commercial Support
+
+If you need commercial support for Chimera contact us at [info@cefriel.com](mailto:info@cefriel.com).
+
 ### License
 
 _Copyright 2020 Cefriel._

diff --git a/chimera-example/README.md b/chimera-example/README.md
@@ -97,7 +97,7 @@ The Camel Context can be enabled by changing the `volume` directive in the docke
 - ./src/main/resources/routes/camel-context-monitor.xml:/home/routes/camel-context.xml
 ```
 
-The endpoint is available at `http://localhost:8888/chimera-demo/metrics` and can be easily configured with Prometheus for scraping. The endpoint exposes default metrics on the JVM and on Camel Routes and Messages. Moreover, the pipeline it's configured to expose also custom metrics: number of lift/roundtrip conversions executed (`counter`), lift/roundtrip conversion timer (`timer`), metrics on the `seda` queues enabled for the different endpoints (`summary`).
+The endpoint is available at `http://localhost:8888/chimera-demo/metrics` and can be easily configured with Prometheus for scraping. The endpoint exposes default metrics on the JVM and on Camel Routes and Messages. Moreover, the pipeline it's configured to expose also custom metrics: number of lift/roundtrip conversions executed (num_executions `counter`), lift/roundtrip conversion timer (processing_time `timer`), metrics on the `seda` queues enabled for the different endpoints (seda_queue_size `summary`). Each metric is tagged using a different `routeId` for the lift and roundtrip conversion endpoints.
 
 The Micrometer registry configuration can be modified in class `MicrometerConfig`. The class `SedaMetricsProcessor` showcases how to define a custom Camel Processor and it is used in the pipeline to feed the related custom metrics.