generated from camel.apache.org/component
Update wiki Home page for micrometer
parent
48ec3e6732
commit
ac70bda372
43
Home.md
43
Home.md
@ -1,21 +1,36 @@
|
||||
# Deploy the Project on CamelX Platform
|
||||
# Micrometer
|
||||
|
||||
Deploy on CamelX Platform in three steps
|
||||
Collect various metrics directly from Camel routes using the Micrometer library.
|
||||
|
||||
## Step 1: Create a release
|
||||
From the project space, click on **"Create a release"**
|
||||
## Metadata
|
||||
|
||||
The new version is automatically available in the list
|
||||
| Property | Value |
|
||||
|----------|-------|
|
||||
| Scheme | `micrometer` |
|
||||
| Support Level | Stable |
|
||||
| Labels | monitoring |
|
||||
| Version | 4.10.2 |
|
||||
|
||||
## Step 2: Deploy
|
||||
Click on **"Deploy"**
|
||||
## Maven Dependency
|
||||
|
||||
- **Version:** Select the desired release
|
||||
- **Environment:** Choose `Development`, `Staging`, or `Production`
|
||||
- **Configuration:** Select the configuration source
|
||||
- **Resources:** Set CPU and Memory
|
||||
```xml
|
||||
<dependency>
|
||||
<groupId>org.apache.camel</groupId>
|
||||
<artifactId>camel-micrometer</artifactId>
|
||||
<version>4.10.2</version>
|
||||
</dependency>
|
||||
```
|
||||
|
||||
## Step 3: Expose
|
||||
Enable **"Expose"**
|
||||
## Endpoint Properties
|
||||
|
||||
Choose an **API Gateway** (Internal, Public, etc.)
|
||||
| Name | Type | Required | Default | Description |
|
||||
|------|------|----------|---------|-------------|
|
||||
| `metricsType` | object | ✓ | | Type of metrics |
|
||||
| `metricsName` | string | ✓ | | Name of metrics |
|
||||
| `tags` | object | | | Tags of metrics |
|
||||
| `action` | string | | | Action expression when using timer type |
|
||||
| `decrement` | string | | | Decrement value expression when using counter type |
|
||||
| `increment` | string | | | Increment value expression when using counter type |
|
||||
| `metricsDescription` | string | | | Description of metrics |
|
||||
| `value` | string | | | Value expression when using histogram type |
|
||||
| `lazyStartProducer` | boolean | | `false` | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
|
||||
|
||||
Loading…
Reference in New Issue
Block a user