I have a task that sends to Kibana a number of files it's supposed to run, then it sends an event for each file that finishes. How can I configure my Kibana to give me a pie chart of remaining files from finished files? (If it's impossible to do with a pie chart I'd like to hear about other charts to do that with)
Ideally if for example I have 20 files and 5 finished I want my pie to be 3 quarters of one color (waiting files) and 1 quarter another color (finished files).
If you're to use the pie chart, you might have to differentiate the file whether it's a finished one or a waiting one by using filter aggregation. You can have a look at this, for more about using the filter.
So in your case, let's assume if you have a field called status which has distinct values as waiting and finished. What you can do is to have two filters containing:
filter 1
status:'waiting'
filter 2
status:'finished'
So the above would actually split your pie chart into two sections where one containing the waiting events and the other containing finished events with two different colors. This is just a thought so that you could reproduce. Hope it helps!
Related
Is it possible to create a custom rule or some other method to automatically move a work item from the DONE state/column to an Area called "Archive" and change the iteration to one of our archive iterations based on a rule? Ultimately we want an automated process to archive work items in the DONE column after a specific date. For example, I set up an Archive area and various archive iterations based on the quarter of the fiscal year. We have a requirement to maintain this documentation for x years and don't want to see it all in the DONE column for years to come.
We have started our new sprint and in burndown trend ( Azure Devops ) we can not see remaing work in the graph.
At the same time in capacity tab, we can see efforts have been planned for the current iteration.
Are we missing anything.
UPDATE 1
Burn down is based on sum of remaining work and every task has value associated with it. In following image you can see remaining work is 106. But still its not reflected in graph.
Note that on the first day of the sprint there's nothing to burndown. If you hover your mouse over to the far left of the chart, it will highlight the work items that will burndown.
There's also a few different options for the chart. Click through the View the full report to see:
Which backlog are you burning down -- Tasks or Stories? or individual work items?
What are you burning down? Count of work items, Sum of completed work or remaining work?
Note, if you're burning down remaining work your tasks will need remaining work filled out to be useful.
We have a list of tasks on the website that all users need to perform before they are able to apply for a job. Tracked by Events
I'm able to create a table by userid that shows all the task that were completed by that user and then I'm able to create a table that shows distinct count of all tasks they've finished.
To count the task events, I've created a new metric
COUNT_DISTINCT(Event Action)
Then using a filter to show the task I'm interested in.
Tasks completed by User:
User ID
Count of Tasks Completed
1
11
2
11
3
11
4
10
5
9
6
9
7
4
8
4
9
4
10
2
What I'd like to do is show a pie chart that display the % of users that completed a certain number of tasks. For example 30% completed 10 tasks, 20% completed 9 tasks, etc.
Took a while, but I finally figured this one out.
First you have to create three new metrics, one to count distinct events and one to count distinct user IDs You need a third to convert the distinct event counts into a usable metric for calculating a completion % and is based on the distinct event counts.
Then I created filters to isolate the specific events I'm interested in.
Since you can't re-aggregate data or apply filters based on a custom metrics in a data source, I created two separate tables with the necessary filters in order to blend the data.
I then blended the data and created the necessary additional filter based on the event count and applied to desired blended source. In this case, I want to see all users with an ID that finished 11 tasks.
Blended table
Blended data source
The final step is divide the total number of desired events / total users to get a completion rate.
And here's the custom metric for that.
This is pretty controverted and took taking several technics from several blog sources and combining them into one work flow.
I am creating a Gantt chart with jasper reports. But in this chart think it as a calendar where we can see some resource allocations. So the resource is a task and the allocations are sub tasks. That means there are multiple sub tasks for a task that are spread through months. If my data set contains data that spreads through about 6 months of a time period then the Gantt is very crowded and the tick labels are overlapping with each other. BTW the ticks should be shown in days. I want to split this report into several pages say 3 months for a page. The sub tasks doesn't have to start and end in one page. It's ok to start in one page and end them in another. So I basically want to print one report and split it to pages. I'm new to Jasper reports. It would be great help if someone can help me with a solution. The chart is getting its data through a sub data set and the data source is a Json.
Thanks
Is there a possibility to create a new chart if a specific number of rows is reached?
Lets say i have 150 entries in my dataset, but the chart is only readable with 50 entries each. How could i do that?
PS: To the Editor i'm working with dynamic-reports which use jasper-reports.
I figured out the following workaround to this problem.
The max size of the DataSources in the list specifies the max rows per chart.
This solution consists of two classes:
The Concenator (Observer)
The ReportGenerator (Runnable or Thread,
Observable)
Visio sketch of the concenator:
http://i.stack.imgur.com/aMmvC.png
The Concenator first generates a list of DataSources with each having a maximum length.
Than for each DataSource in the list a ReportGenerator will be started, he also will get the pagenumber (for final sorting after collection).
The Concenator waits until every reportpage is delivered.
Whenn every page is collected the concenator sorts the pages according to the number and then stick them together page by page.
PS: I have an visio sketch ready but less reputation for posting it directly.