Over the years, we have established ourselves as a trusted outsourcing partner, backed by a highly skilled and dedicated team of professionals committed to delivering accurate, timely, and cost-effective results. Our expertise spans a wide range of services, including Data Entry, Data Processing, Finance & Accounting, Virtual Assistance, Document Digitization, Data Automation, and E-commerce Solutions. By combining industry expertise with advanced technology, we continue to provide comprehensive and customized outsourcing services, making us the Best BPO Agency in USA, India for businesses seeking reliable and scalable solutions.

Currently, the Monitor tab provides a consolidated view of several important metrics, such as overall performance and errors, which makes it a very useful place to understand the health of an application. However, there is currently no equivalent visibility into the Real-Time layer.

For applications that rely on WebSockets and Real-Time features, it would be extremely valuable to have a dedicated monitoring section similar to Performance Insights, focused specifically on Real-Time activity. This section could display metrics such as the number of connected users/sessions, active channels, messages received, events published, connection/disconnection rates, and historical trends over time.

Having this information available in a centralized monitoring dashboard would make it much easier to understand system usage, troubleshoot issues, identify unusual activity, and evaluate the adoption of Real-Time features. At the moment, there is no consolidated way to observe what is happening within the Real-Time infrastructure, and adding such a view would significantly improve observability for applications that depend on WebSockets.

FA

A dedicated Redis monitoring section could provide insights such as the total number of keys, key creation and deletion rates, storage utilization, memory consumption trends, cache hit and miss rates, expiration activity, and historical usage patterns over time. It could also help identify unexpected growth in key counts, excessive key churn, inefficient cache usage, or storage-related issues before they impact application performance.

Having these metrics available directly within the Monitor dashboard would make it much easier to understand how Redis is being used across an application and to troubleshoot performance or scaling issues. Currently, there is limited visibility into Redis activity, and a dedicated monitoring view would significantly improve operational awareness and platform observability.

FA

Im using the 2FA via google authenticator. I tried signing in this morning and my 2FA code kept getting rejected. I verified Im getting the right code and that I didnt have any mistake on my end. I tried it several times till my 6th attempt got me inside the app. All 5 first attempts got rejeceted even though I was using the right code 100%

4 hours later - again same issue

Im trying again now and it keeps on failing. Its been a about 4 hours since the above attempt. Now It keeps rejecting ky 2FA codes constantly

This is what i get every time:

Please help.. Im locked out

Thanks!

Omer

A dedicated Redis monitoring section could provide insights such as the total number of keys, key creation and deletion rates, storage utilization, memory consumption trends, cache hit and miss rates, expiration activity, and historical usage patterns over time. It could also help identify unexpected growth in key counts, excessive key churn, inefficient cache usage, or storage-related issues before they impact application performance.

Having these metrics available directly within the Monitor dashboard would make it much easier to understand how Redis is being used across an application and to troubleshoot performance or scaling issues. Currently, there is limited visibility into Redis activity, and a dedicated monitoring view would significantly improve operational awareness and platform observability.

FA

Currently, the Monitor tab provides a consolidated view of several important metrics, such as overall performance and errors, which makes it a very useful place to understand the health of an application. However, there is currently no equivalent visibility into the Real-Time layer.

For applications that rely on WebSockets and Real-Time features, it would be extremely valuable to have a dedicated monitoring section similar to Performance Insights, focused specifically on Real-Time activity. This section could display metrics such as the number of connected users/sessions, active channels, messages received, events published, connection/disconnection rates, and historical trends over time.

Having this information available in a centralized monitoring dashboard would make it much easier to understand system usage, troubleshoot issues, identify unusual activity, and evaluate the adoption of Real-Time features. At the moment, there is no consolidated way to observe what is happening within the Real-Time infrastructure, and adding such a view would significantly improve observability for applications that depend on WebSockets.

FA

From a usability and consistency standpoint, this feels a bit confusing, because it creates the impression that the trigger exists in isolation and is not part of the overall triggers system. It would be more intuitive if error log triggers were also visible in the Triggers tab alongside the others, so that all automation logic could be managed and reviewed in one place. This would make it easier to audit, maintain, and understand all active triggers in a project without having to check multiple sections of the interface.

FA