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

Allow users to manage reports #17878

Closed
3 of 4 tasks
elasticmachine opened this issue Feb 10, 2017 · 8 comments
Closed
3 of 4 tasks

Allow users to manage reports #17878

elasticmachine opened this issue Feb 10, 2017 · 8 comments
Labels
(Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead Feature:Reporting:Framework Reporting issues pertaining to the overall framework needs-team Issues missing a team label release_note:enhancement

Comments

@elasticmachine
Copy link
Contributor

elasticmachine commented Feb 10, 2017

Original comment by @w33ble:

The async queue UI brought in LINK REDACTED could use a lot more controls. For example:

@elasticmachine
Copy link
Contributor Author

Original comment by @tbragin:

I think that in addition to deletion, we should consider other report management tasks, such as searching, sorting, and filtering. Making the title more general to reflect that.

@elasticmachine
Copy link
Contributor Author

Original comment by @tbragin:

via @bohyun-e from LINK REDACTED

from discuss: https://discuss.elastic.co/t/provide-more-control-over-report-generation/57880
Stopping the report generation
Pausing a report generation
Clearing all the documents present in Generated reports (Or provide control of deleting a single created report)

@elasticmachine
Copy link
Contributor Author

Original comment by @tbragin:

One thing I noticed playing with managing report history via Sense is that right now the way the reporting index is organized, one has to either delete the whole weekly index or delete individual reports by its Elasticsearch document id (_id) -- there is no way to filter the index by report title (payload.title)or Kibana id (payload.id).

From a workflow perspective, it seems natural to want to filter a long report history by report title before determining which reports to delete, but for that we'll have to index the right fields with correct mappings.
screen shot 2016-08-22 at 2 35 57 pm

Note: If we don't make the data-level changes to enable this for 4.6, and decide to do this in 5.0, we'll may have to ask users to delete their report history on migration or think through report index versioning.

Representative report document for reference:

      {
        "_index": ".reporting-2016-08-21",
        "_type": "esqueue",
        "_id": "is6ihsf208mjff16dec9blls",
        "_score": 0.30685282,
        "_source": {
          "jobtype": "printable_pdf",
          "payload": {
            "id": "Metric-2",
            "title": "Metric 2",
            "description": "Oh, what a night\nHypnotizing, mesmerizing me\nShe was everything I dreamed she'd be\nSweet surrender, what a night",
            "type": "visualization",
            "objects": [
              {
                "id": "Metric-2",
                "type": "visualization",
                "searchSource": {
                  "index": "logstash-2014*",
                  "query": {
                    "query_string": {
                      "query": "*",
                      "analyze_wildcard": true
                    }
                  },
                  "filter": []
                },
                "uiState": {},
                "isUsingTimeBasedIndexPattern": true,
                "url": "http://0.0.0.0:5601/app/kibana#/visualize/edit/Metric-2?_g=(time:(from:'2014-09-16T21:57:41.882Z',mode:quick,to:'2014-09-23T00:43:45.155Z'))&_a=(filters:!(),linked:!f,query:(query_string:(analyze_wildcard:!t,query:'*')),uiState:(),vis:(aggs:!((id:'1',params:(field:bytes,values:!(1,50,75,80,90,95)),schema:metric,type:percentile_ranks)),listeners:(),params:(fontSize:60,handleNoResults:!t),title:'Metric%202',type:metric))",
                "title": "Metric 2",
                "description": "Oh, what a night\nHypnotizing, mesmerizing me\nShe was everything I dreamed she'd be\nSweet surrender, what a night"
              }
            ],
            "date": "2016-08-22T20:45:19.189Z",
            "query": {
              "_g": "(time:(from:'2014-09-16T21:57:41.882Z',mode:quick,to:'2014-09-23T00:43:45.155Z'))",
              "_a": "(filters:!(),linked:!f,query:(query_string:(analyze_wildcard:!t,query:'*')),uiState:(),vis:(aggs:!((id:'1',params:(field:bytes,values:!(1,50,75,80,90,95)),schema:metric,type:percentile_ranks)),listeners:(),params:(fontSize:60,handleNoResults:!t),title:'Metric 2',type:metric))"
            },
            "headers": {}
          },
          "priority": 10,
          "created_by": false,
          "timeout": 30000,
          "process_expiration": "2016-08-22T20:45:51.390Z",
          "created_at": "2016-08-22T20:45:19.263Z",
          "attempts": 1,
          "max_attempts": 3,
          "status": "completed",
          "started_at": "2016-08-22T20:45:21.390Z",
          "output": {
            "content_type": "application/pdf",
            "content": "JVBERi0xLjMKJf////8KOCAwIG9iago8PAovUHJlZGljdG9yIDE1Ci9...truncated"
          },
          "completed_at": "2016-08-22T20:45:29.872Z"
        }
      }

mapping for payload:

          "payload": {
            "type": "object",
            "enabled": false
          }

@stacey-gammon
Copy link
Contributor

Requested in #19752 is ability to rename the file in management.

@timroes timroes added Team:Visualizations Visualization editors, elastic-charts and infrastructure and removed :Sharing labels Sep 13, 2018
@timroes timroes added Team:Stack Services and removed Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Jul 18, 2019
@bmcconaghy bmcconaghy added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) and removed Team:Stack Services labels Dec 12, 2019
@bmcconaghy bmcconaghy added Team:Reporting Services and removed Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Dec 20, 2019
@elasticmachine
Copy link
Contributor Author

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

@bruno-lopes
Copy link

bruno-lopes commented Nov 27, 2020

Any news on that? Would it be possible to release at least the delete report button?

UPDATE: Sorry, now I saw that I can select the report and remove it. Thanks.

@elasticmachine
Copy link
Contributor Author

Pinging @elastic/kibana-app-services (Team:AppServices)

@tsullivan
Copy link
Member

Closing for #81544

@sophiec20 sophiec20 added the Feature:Reporting:Framework Reporting issues pertaining to the overall framework label Aug 21, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
(Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead Feature:Reporting:Framework Reporting issues pertaining to the overall framework needs-team Issues missing a team label release_note:enhancement
Projects
None yet
Development

No branches or pull requests

7 participants