You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2022/10/24 10:04:00 UTC
[jira] [Commented] (CAMEL-18645) camel-health - Details metadata is mixed between custom and standard details
[ https://issues.apache.org/jira/browse/CAMEL-18645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623090#comment-17623090 ]
Claus Ibsen commented on CAMEL-18645:
-------------------------------------
You can use isReservedKey on HealthCheckHelper to know if its a standard or not
> camel-health - Details metadata is mixed between custom and standard details
> ----------------------------------------------------------------------------
>
> Key: CAMEL-18645
> URL: https://issues.apache.org/jira/browse/CAMEL-18645
> Project: Camel
> Issue Type: Improvement
> Components: camel-health
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 3.x
>
>
> If you want to output custom meta-data then you need to filter out the standard keys.
> {code}
> "details": {
> "invocation.count": "179",
> "failure.time": "2022-10-24T11:00:40.295336+02:00[Europe/Oslo]",
> "group.id": "5b6145fb-3bcd-4d91-be53-12c144fc9950",
> "bootstrap.servers": "value",
> "invocation.time": "2022-10-24T11:00:40.295336+02:00[Europe/Oslo]",
> "check.group": "camel",
> "route.id": "kafka-not-secured-source-1",
> "failure.start.time": "2022-10-24T10:54:41.812377+02:00[Europe/Oslo]",
> "topic": "value",
> "success.count": "0",
> "check.id": "kafka-consumer-kafka-not-secured-source-1",
> "check.kind": "READINESS",
> "failure.count": "179"
> }
> }
> {code}
> In the example above then custom is topic and bootstrap.servers. All the other is standard by camel-health.
> We may consider having reserved keys by camel, and for custom to better separate this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)