Manage Event Stream Viewer default settings in Logger Parameters

[steven-hayhurst-tesco]

New Feature Summary

I'd like to be able to customise some of the default values in the Event Stream viewer so that my custom values are automatically entered into the filters upon loading the component.

Why? Our org is a heavy user of platform events and we'd like to minimise the amount of events unnecessarily delivered. Currently the event viewer will listen for up-to 500 events by default. This is hard-coded into the LWC. Also by default it will listen for all event levels.

We'd like to be able to set values in Logger Parameters in order to customise these values and limit what the stream listens to by default, in order to reduce consumption of limits.

[jongpie]

Hi @steven-hayhurst-tesco this sounds like a good idea to me - the streaming component has caused limits issues for multiple orgs/people in the past, so making some of the default values configurable sounds useful for a lot of people.

It sounds like there should be 2 new configuration options:

1. Max Number of Events to Stream: currently hardcoded to 500. Making this configurable will directly impact (improve) the number of events delivered
2. Minimum Logging Level: this filter doesn't affect the number of platform events streamed - all LogEntryEvent__e records are delivered to the component, and then filters like this one are applied afterwards. I like making this particular filter value configurable, but it's important to note that it won't actually reduce the consumption of platform event subscriptions.

For all of the other filters, I think they can continue to function as-is - but let me know if you have any other suggestions!

---

And for anyone reading along, here's a screenshot of the streaming component for reference:

[steven-hayhurst-tesco]

Great thanks for jumping on this so quickly. And for pointing out that controlling the logging level won't actually reduce what's delivered. Oversight on my part so thanks for clearing that up!
I agree that the other values are fine left as they are. The only other thing I considered is whether the Max Number of Events to Stream should have a ceiling, ie, we don't want someone typing 50000 then walking away. Sounds like something so stupid that it would never happen, but I've seen more unlikely things happen in my career! We could either set an absolute max value that cannot be listened past, or perhaps a time limit? ie the component will automatically unsubscribe after, say, 5 minutes.

[steven-hayhurst-tesco]

I've never used this myself, but I've just been reading about Platform Event Channels. Potentially a way to limit the actual messages delivered in the LWC, but would presumably be a bit more work than this simple change.