Add log level support

[Anntoin]

We've found that recordError is a useful replacement for custom client error logging. However to completely replace what we have now we'd need support for other log levels, e.g. info, warn.

This could be provided by a recordLog or recordEvent command that supports arbitrary logging. Is this something that would be considered in scope for the rum client?

[qhanam]

Hi @Anntoin thanks for raising this (and sorry taking so long to respond)! I agree these are important use cases.

For both recordLog and recordEvent, the CloudWatch RUM service must first support these application-specific event types. Currently, it only supports a fixed set of events.

For example, it is currently possible to use the CloudWatch RUM web client (by creating a plugin) or the CloudWatch RUM SDK to send arbitrary events to CloudWatch RUM, however only those events which conform to an accepted schema will be ingested (the rest will be dropped).

We will update this thread when CloudWatch RUM has added support, but I can't provide an ETA.

[maniator]

I am going to see if it is possible to add a recordEvent method to go according to the RUM schema here: https://docs.aws.amazon.com/cloudwatchrum/latest/APIReference/API_PutRumEvents.html

[maniator]

@Anntoin see #185 for possible solution :-)

[Anntoin]

That's awesome 🎉 thanks for following up! This should cover our use case. I'm on vacation at the moment but looking forward to checking it out when I get back. This makes RUM a one-stop shop for all our client-side visibility needs!

…

On Tue 26 Jul 2022, 19:53 Naftali Lubin, ***@***.***> wrote: @Anntoin <https://github.com/Anntoin> see #185 <#185> for possible solution :-) — Reply to this email directly, view it on GitHub <#139 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZC7QZCV2QBN4EO22RSBPLVWAXZPANCNFSM5USNF4LA> . You are receiving this because you were mentioned.Message ID: ***@***.***>