Closed robrap closed 1 year ago
I asked something like the following of both Confluent and New Relic, and will post answers later.
I’m wondering about monitoring our Confluent Cloud usage in New Relic.
I'd like to add a set_custom_attributes
call for the message id in the consumer. I asked if that could be done as part of the CloudEvents ticket here: https://github.com/openedx/openedx-events/issues/77#issuecomment-1332761300. If not, maybe add a new task. Either way, maybe this task could be closed.
Created the new task https://github.com/edx/edx-arch-experiments/issues/121 for new custom attributes. Closing this discovery.
Document the various needs for observability, and make recommendations and ticket what is needed immediately, and what can be deferred.
Some earlier notes on observability:
From https://www.infoworld.com/article/3269207/busting-event-driven-myths.html:
Also note, although we don't want to fully implement CloudEvents, any fields required for observability that are defined in the OEP for CloudEvents should be used where possible. See https://github.com/openedx/openedx-events/issues/77. This may include an event id, for example, although I'm not clear on whether or not Kafka also includes an event id.