[CAMEL-18645] camel-health - Details metadata is mixed between custom and standard details

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 3.20.0
• Component/s: camel-health
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Claus Ibsen
• Created: 24/Oct/22 09:43
• Updated: 24/Oct/22 10:03
• Resolved: 24/Oct/22 10:03

Description

If you want to output custom meta-data then you need to filter out the standard keys.

       "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"
        }
      }

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.