Bug: Journal service cannot handle certain SuperMQ messages

[unwynd]

What were you trying to achieve?

To process and store journal entries for messaging.client_publish operations using the journal service.

What are the expected results?

All messages, including those received via SuperMQ (NATS), should be correctly handled and journaled.
No warnings or errors should occur if the message is valid.

What are the received results?

Some journal entries succeed.
Others fail with a warning: Failed to handle SuperMQ message: failed to handle nats event: missing attributes

Steps To Reproduce

1. Run the journal service in a Docker container.
2. Publish messages.
3. Observe logs for successful saves and any warning messages.
4. Confirm if the failed message is lacking required attributes.

In what environment did you encounter the issue?

Environment: Docker

Additional information you deem important

Successful logs indicate normal behavior:

{"msg":"Save journal completed successfully","operation":"messaging.client_publish"}

The failing log includes: "msg":"Failed to handle SuperMQ message: failed to handle nats event: missing attributes"

Even though the journal service logs a successful Save journal completed successfully message for messaging.client_publish operations, the corresponding entries do not appear in the audit logs.

[unwynd]

The issue was observed following #2858.

However, I believe the error Failed to handle SuperMQ message: failed to handle NATS event: missing attributes was observed before the mentioned PR.

[liar557]

I also encountered this problem, may I ask if you have resolved it?

[unwynd]

@liar557 No, I still see the issue with the latest main.

[felixgateru]

Hello @unwynd
The "msg":"Failed to handle SuperMQ message: failed to handle nats event: missing attributes" issue should be resolved by this pr: #2890

For this: Even though the journal service logs a successful Save journal completed successfully message for messaging.client_publish operations, the corresponding entries do not appear in the audit logs. The messaging.client_publish logs are meant to be used to generate client's telemetry hence no longer appear in any entities' audit logs.You can access this feature through our API via the curl command:

curl --location 'http://localhost:9021/<domain_id>/journal/client/<client_id>/telemetry' \ --header 'Authorization: Bearer <access_token>'

This feature is based on the Journal service. Please make sure it is running.
You can expect a response that looks like this:

[unwynd]

Hello @felixgateru,

Thanks for the clarification. I’ve updated (#2938) the OpenAPI document to reflect the API changes.