ENVs introduced -
| `ENV` | Description |
|--------|-------------|
| `ZO_USAGE_REPORTING_MODE` | Possible values - `local`, `remote` and
`both`. `local` means usage is only reported in internal cluster.
`remote` means store it in remote address and `both` means reporting is
done in the both `local` and `remote`. Default is `local` |
| `ZO_USAGE_REPORTING_URL` | Remote Reporting URL (with full api
endpoint). Default is `http://localhost:5080/api/_meta/usage/_json` |
| `ZO_USAGE_REPORTING_CREDS` | Credentials required for posting the
usage report to remote reporting URL |
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.
- Verify if quick mode is displayed
- Verify if user is able to click on interesting fields
- Verify on clicking interesting fields user is able to view the field
in sql mode
- Verify if on clicking interesting field when histogram is enabled,
expected results are displayed
- Verify if error displayed on entering random text in histogram mode
when quick mode is on
- Verify should display order by as default when switched to sql mode
- Verify if on page refresh the orderby is still present by default in
sql mode
- Verify if on page adding removing the interesting field removes in
from sql mode and the results too
Instead of waiting for `CONFIG.chrome.chrome_sleep_secs` to let the data
load in the dashboard for report, frequently, check for the `span`
element with a loop.
Ashish Kolhe
Omkar Kesarkhane
Hengfei Yang
dependabot[bot]
HuaijinandHengfei Yang
Subhra264
Yonas Yanfa
Prabhat Sharma
RanolP
胡同里有猫
Ankur Srivastava
xiaoziv
ktx-vaidehi
deterclosed
dongjinlong
Neha P
