# Websocket Disconnected Because DataFrame/Message Too Large with Perspective

**URL:** <https://forum.inductiveautomation.com/t/websocket-disconnected-because-dataframe-message-too-large-with-perspective/67391>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [December 8, 2022, 5:55pm UTC](https://forum.inductiveautomation.com/t/websocket-disconnected-because-dataframe-message-too-large-with-perspective/67391 "2022-12-08T17:55:43Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![tcrucet](https://avatars.discourse-cdn.com/v4/letter/t/76d3ee/32.png) [@tcrucet](https://forum.inductiveautomation.com/u/tcrucet)\
**Post date:** [June 12, 2023, 3:56pm UTC](https://forum.inductiveautomation.com/t/websocket-disconnected-because-dataframe-message-too-large-with-perspective/67391/5 "2023-06-12T15:56:50Z")

</div>

I forgot to follow up on the issue here. The solution to my particular problem was to not use the native filter, but to instead filter using the filterAlarm extended function, which is a lot faster:

```auto
return "Active" == str(alarmEvent.get('EventState'))

```

---

_[View the full topic](https://forum.inductiveautomation.com/t/websocket-disconnected-because-dataframe-message-too-large-with-perspective/67391)._