Subscription: {{subscription.name}}

Endpoint: {{subscription.endpoint}}

Team: {{subscription.supportTeam}} Contact: {{subscription.contact}}

{{subscription.description}}

{{subscription.state}}

Subscription health problems

Subscription lag is growing. Examine output rate and service response codes, looks like it is not consuming at full speed.

Consumption rate is lower than topic production rate. Examine output rate and service response codes. If everything is well, take a look at maximum rate, maybe it is too low?

Consuming service returns a lot of 5xx codes. Looks like it might be malfunctioning or doesn't know how to handle messages. Take a look at "Last undelivered message" for more information.

Consuming service returns a lot of 4xx codes. Maybe you are receiving some malformed messages? If this is normal behavior, switch Retry on 4xx status flag to false. This way Hermes will not try to resend malformed messages, reducing traffic.

Consuming service times out a lot. Hermes times out after 1 second, if you are not able to process message during this time, connection is reset and delivery fails.

Unable to connect to consuming service instances. It is either network issue or your service instance is down.

Subscription metrics

Delivery rate: {{metrics.rate | number:2}}

Delivered: {{metrics.delivered}}

Discarded: {{metrics.discarded}}

Lag: {{metrics.lag}}

Output rate

Service response metrics

Properties

Content type: {{subscription.contentType}}

Delivery type: {{subscription.deliveryType}}

Mode: {{subscription.mode}}

Rate limit: {{subscription.subscriptionPolicy.rate}}

Batch size: {{subscription.subscriptionPolicy.batchSize}} messages

Batch time window: {{subscription.subscriptionPolicy.batchTime}} milliseconds

Batch volume: {{subscription.subscriptionPolicy.batchVolume}} bytes

Request timeout: {{subscription.subscriptionPolicy.requestTimeout}} milliseconds

Message TTL: {{subscription.subscriptionPolicy.messageTtl}} seconds

Tracking enabled: {{subscription.trackingEnabled}}

Retry on 4xx status: {{subscription.subscriptionPolicy.retryClientErrors}}

Retry backoff: {{subscription.subscriptionPolicy.messageBackoff}} milliseconds

Monitoring severity: {{subscription.monitoringDetails.severity}}

Monitoring reaction: {{subscription.monitoringDetails.reaction}}

{{entry.title}}: {{entry.options[subscription.endpointAddressResolverMetadata[key]] || subscription.endpointAddressResolverMetadata[key]}}

{{key}}: {{value}}

Messages retransmission

Last undelivered message

Time: {{lastUndelivered.timestamp | date:'yyyy-MM-dd HH:mm:ss'}}

Reason: {{lastUndelivered.reason}}

Message:

{{lastUndelivered.message}}
                        

Show event trace

 
Phase Time Status
{{trace.subscription ? 'SENDING' : 'RECEIVING'}} {{trace.timestamp | date:'yyyy-MM-dd HH:mm:ss.sss'}} {{trace.status}} {{trace.status != 'SUCCESS' ? trace.reason : ''}}

No matches found - is the id correct? Remember we keep traces for 14 days.

Last 100 undelivered messages

# MessageId Status Reason Timestamp
{{$index + 1}} {{msglog.messageId}} {{msglog.status}} {{msglog.reason}} {{msglog.timestamp | date:'yyyy-MM-dd HH:mm:ss'}}