Due to changes in the current architecture the access-token is being
sent as a cookie - `access_token` so this change facilitates accessing
the proxy url via the same mechanism
---------
Co-authored-by: omkark06 <omkar@zinclabs.io>
**Problem**:
Histogram was disabled in SQL mode.
**Solution**:
Enabled histogram in sql mode for only non aggregated queries
---------
Co-authored-by: Bhargav <BJP232004@GMAIL.COM>
Problem:
Suppose we want to give POST permission for all log streams. Then we use
orgId as entity, as we give permission for all log streams in that org.
If orgId and stream name are same. For eg. default log stream in default
org. The permission object for post permission on single "default" (name
of stream) log stream and Post permission on all log streams in
"default" org, both are same. And this creates a conflict
Solution:
While giving all resources permission on any of resource type, we prefix
orgId with `_all_` and this will not conflict with any resource
---------
Co-authored-by: oasisk <ashish.j.kolhe@gmail.com>
Sharing dashboard URLs didn't work properly when tabs were involved.
Regardless of the selected tab, the link always took users to the first
tab. This issue has been fixed, ensuring that shared URLs now correctly
direct users to the intended tab, providing a smoother experience for
navigating dashboards.
In sql mode, if query does not contains " order by " it throws error.
Solution:
On switching to sql mode, by default added "order by _timestamp desc" in
logs query
While implementing a filter search feature with dropdown menus for
variables, an error occurred due to undefined values. This error
hindered the functionality of the search feature, causing unexpected
behavior when attempting to filter results.
- The notification has been eliminated during the configuration of
absolute dates.
- The SQL mode should not trigger the query automatically upon
deactivation if run query flag is true.
- The Histogram feature should remain inactive while SQL mode is
enabled.
- Modifications related to the quick mode.
- Within SQL mode, the "_timestamp" field is required, and an "order by"
clause is necessary.
---------
Co-authored-by: Hengfei Yang <hengfei.yang@gmail.com>
Problem:
Observed that the User Session Viewer was yielding incorrect results
when filtering session events data. The root cause was identified as the
improper handling of a compound predicate within the SQL query used for
data retrieval.
Solution:
When parentheses were added around the conditions `session_id='xyz' &&
(type='error' or type='action' or type='view')` to logically group them,
this fixed the issue.
Ashish Kolheandomkark06
Bhargav
ktx-vaidehi
ktx-abhay
Ankur Srivastavaandomkark06
Omkar KesarkhaneandBhargav
Hengfei Yang
deterclosed
dongjinlong
Subhra264andomkark06
