Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Reports do not respect dates and contain errors when using absolute date range #204

Closed
TonyLovesDevOps opened this issue Oct 29, 2021 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@TonyLovesDevOps
Copy link

Describe the bug

Generating a report from a dashboard when specifying an absolute date range fails to show the requested date range and the report contains errors showing Error restoring state from URL rison decoder error: missing ':'.

To Reproduce
Steps to reproduce the behavior:

  1. Launch a fresh 1.1.0 OpenSearch and OpenSearch Dashboards cluster
  2. Load the sample eCommerce data
  3. Open the sample [eCommerce] Revenue Dashboard dashboard
  4. Specify an absolute date from, for example from October 1, 2021 @ 00:00:00.000 to now
  5. Click Reporting > Download PDF Report (also happens w/ PNG reports)

Expected behavior
Report shows absolute date range specified in the dashboard and does not contain errors

OpenSearch Version
1.1.0 (via opensearchproject/opensearch:1.1.0 docker image)

  "version" : {
    "distribution" : "opensearch",
    "number" : "1.1.0",
    "build_type" : "tar",
    "build_hash" : "15e9f137622d878b79103df8f82d78d782b686a1",
    "build_date" : "2021-10-04T21:29:03.079792Z",
    "build_snapshot" : false,
    "lucene_version" : "8.9.0",
    "minimum_wire_compatibility_version" : "6.8.0",
    "minimum_index_compatibility_version" : "6.0.0-beta1"
  }

Dashboards Version
1.1.0 (via opensearchproject/opensearch-dashboards:1.1.0 docker image)

Plugins
Defaults -- from _cat/plugins API endpoint:

opensearch-alerting                  1.1.0.0
opensearch-anomaly-detection         1.1.0.0
opensearch-asynchronous-search       1.1.0.0
opensearch-cross-cluster-replication 1.1.0.0
opensearch-index-management          1.1.0.0
opensearch-job-scheduler             1.1.0.0
opensearch-knn                       1.1.0.0
opensearch-notebooks                 1.1.0.0
opensearch-performance-analyzer      1.1.0.0
opensearch-reports-scheduler         1.1.0.0
opensearch-security                  1.1.0.0
opensearch-sql                       1.1.0.0

Screenshots

Here's a PNG report of an attempt to export the date range from October 1, 2021 @ 00:00:00.000 to now. Note the errors in the lower right and that the date range shows Last 7 days instead of the requested range.

On_demand_report_with_errors

Host/Environment (please complete the following information):

Additional context

This may be fixed by #153 (and potentially just another symptom of issues #61 and/or #88).

@davidcui1225
Copy link
Contributor

I tested this with the same eCommerce dashboard and set the absolute date to November 1 and I get the correct time range with no errors in my report. Can you confirm that you still see this issue?

@TonyLovesDevOps
Copy link
Author

TonyLovesDevOps commented Nov 17, 2021

I tested this with the same eCommerce dashboard and set the absolute date to November 1 and I get the correct time range with no errors in my report. Can you confirm that you still see this issue?

Thanks for investigating! I just tried this again using the example docker-compose.yaml file and I can still repro the issue.

@TonyLovesDevOps
Copy link
Author

Here's a screencast of the repro using the sample data...
repro

@zhongnansu
Copy link
Member

I am able to reproduce the issue in the 1.1 version, but it seems to be fixed in 1.2. Please use the latest version and try

@TonyLovesDevOps
Copy link
Author

@zhongnansu thanks for verifying that. I can confirm that the issue is fixed in 1.2.0 running locally.

Do you have any visibility into when 1.2 might be available on AWS OpenSearch? I've asked in the OpenSearch Forum and on the AWS forum and have heard "we don't know" and 🦗 🦗 , respectively.

@zhongnansu
Copy link
Member

zhongnansu commented Nov 24, 2021

@zhongnansu thanks for verifying that. I can confirm that the issue is fixed in 1.2.0 running locally.

Do you have any visibility into when 1.2 might be available on AWS OpenSearch? I've asked in the OpenSearch Forum and on the AWS forum and have heard "we don't know" and 🦗 🦗 , respectively.

@zhongnansu Sorry, like the answer in the the Opensearch forum says, we don't have a fixed date here for AWS Opensearch release. But I think the long term goal is to have AWS and opensource release at the same day : )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants