Currently we log crash reports into crashlytics. Our product activation is dependent on how smoothly first 2 week goes with the product. I am trying to track any specific bugs our user are facing and their frequency for users in their first few weeks. Also if there are any bugs which leads to churn of our active users from our B2B app. Currently our support ticket systems are broken, hence I have to rely on this source of data.
It's not possible to bulk export crash reports from Fabric, according to their docs:
Crash reports can be downloaded for any individual session by pressing
the “View all sessions” and clicking the “Download .txt” button.
Crash reports are currently not available for consumption via an API.
However, there is a way around this. It's not easy, but it'll get you there:
Migrate your project to Firebase (which you'll have to do soon anyway).
Connect your Firebase project to Google BigQuery.
Your Crash data is now available in a SQL-style database.
From there, you can fine tune a SQL query (full table schema) to pull out whatever data you want. There are examples available, such as #2 which sounds very similar to your requirements:
To properly prioritize production plans, a project manager at
PineapplePlusPlus ponders how to point out the most pervasive crashes
in their product. They produce a query that provides the pertinent
points of data:
SELECT
DISTINCT issue_id,
COUNT(DISTINCT event_id) AS number_of_crashes,
COUNT(DISTINCT installation_uuid) AS number_of_impacted_user,
blame_frame.file,
blame_frame.line
FROM
`projectId.crashlytics.package_name_ANDROID`
WHERE
event_timestamp >= TIMESTAMP_SUB(CURRENT_TIMESTAMP(),INTERVAL 168 HOUR)
AND event_timestamp < CURRENT_TIMESTAMP()
GROUP BY
issue_id,
blame_frame.file,
blame_frame.line
ORDER BY
number_of_crashes DESC
LIMIT
10;
You can export Crashlytics Data to BigQuery.
And you can do Sql in BigQuery. It's very easy to use. Free limit to 10G data.
https://firebase.google.com/docs/crashlytics/bigquery-export
Related
In Youtrack reports, you can view the issues by two fields using creation date as y-axis and any other field as x-axis. But when you do that like in this graph you view number of issues that are currently in the state stated in x-axis. For example, if the x-axis is the state, then you will see the current states of the issues that are created in the date intervals of the y-axis. But I also want to see the number of issues in each state in a chronological way. I want to see the states (or some other field) of the issues in May 21, 2021 (not their current states but their states in May 21).
I know that Youtrack keeps the state changes and their dates and many other data like that because in different reports, I can see that the Youtrack uses past data but usually there is no way to download the data of those reports.
I want to access all those raw data. My plan is to create some reports that are not available in Youtrack Reports, using R or Python. Is there a way to access those raw data, or a guideline to access them?
The way to access raw data in YouTrack is through the REST API. For example, you can get the issue's activity data to retrieve the history of changes applied to the issue. This way you can identify how things have changed chronologically.
I can see that the Youtrack uses past data but usually there is no way to download the data of those reports.
Report's data can be accessed via API as well. The report's API endpoint is api/reports, however, it's not documented as it may be subject to change. In this case, we can't guarantee backward compatibility. If you are fine with it, you can still use it. To see the exact request, check the network requests in the browser when loading a report.
Is there a way in native SQL, SQL database specific (i.e. PostGresQL) or another (NoSQL database) to subscribe to query and receive updates when a entry matches the criteria? For example I have the query: SELECT * FROM users WHERE birthday = today() is it possible to receive update when a entry matches the criteria instead of using the so called 'pulling' mechanism? The query can be slightly more complex because this idea is required for a solution which send recurring messages based on the user preferences.
The only database I know that has built-in notifications like this is RebirthDB with a feature called "changefeeds":
They allow clients to receive changes on a table, a single document,
or even the results from a specific query as they happen. Nearly any
ReQL query can be turned into a changefeed.
The only problem is that the database began life as RethinkDB, but the company making it folded in 2016, leaving it to the open-source community. It's still alive as "RebirthDB" on GitHub with active development, but the documentation is just a copy of the old Rethink docs with GitHub notices. They have a website url, but no website. I hope they can keep it alive: it's a great idea.
https://github.com/RebirthDB/docs
My organisation recently applied an update to TFS 2015 (14.102.25423.0 according to the 'About' page of the web interface) that resulted in the 'My Work' tab in Visual Studio 2015 taking up to one minute to populate. I played around with the queries and managed to narrow the problem down to population of the 'Incoming Requests' section of that tab. Under the hood, this is executing the following WIQL query.
SELECT [System.Id], [System.Links.LinkType], [System.Title], [System.State], [System.Reason], [System.AssignedTo]
FROM WorkItemLinks
WHERE (Source.[System.TeamProject] = #project and Source.[System.WorkItemType] in group 'Microsoft.CodeReviewRequestCategory' and Source.[System.AssignedTo] <> #me and Source.[Microsoft.VSTS.Common.StateCode] <> '1')
and ([System.Links.LinkType] = 'System.LinkTypes.Hierarchy-Forward')
and (Target.[System.WorkItemType] in group 'Microsoft.CodeReviewResponseCategory' and (Target.[System.AssignedTo] = #me or Target.[Microsoft.VSTS.Common.ReviewedBy] = #me) and Target.[Microsoft.VSTS.Common.StateCode] <> '2')
ORDER BY [System.CreatedDate] desc, [System.Id] mode(MustContain)
I've reproduced the slowness using the TFS REST API described in https://www.visualstudio.com/en-us/docs/integrate/api/wit/wiql (passing the WIQL query above in the body of the POST request).
The following code review selectors are slow to populate: My Code Reviews & Requests, Incoming Requests.
The following code review selectors are fast to populate: My Code Reviews, Recently Finished, Recently Closed.
The problem is occurring for all users, not just my user.
No one on the team has more than a few code reviews open at any one time.
The problem started occurring practically overnight i.e. on Friday the queries were completing in a second or so, on Monday the queries were taking up to a minute.
Our TFS environment is hosted on Windows Server 2012 (non-R2).
Our TFS environment is backed by SQL Server 2012, SP3 (11.0.6020).
The upgrade to TFS2015.3 was completed as per Microsoft instructions and no issues were encountered and there are no messages in the logs to indicate anything is wrong.
Does anybody have any suggestions about what might be causing this slowness and what can be checked in order to narrow the performance problem down further?
The Team Explorer in Visual Studio provides a dropdown selector for specifying which state of code reviews one wants to list. The available choices are:
My Code Reviews and Requests (open)
My Code Reviews (open/mine)
Incoming Requests (open/others)
Recently Closed (closed)
Recently Finished (finished)
( Annotated each entry above with the state and ownership for clarity.)
According to the description of your performance issue, since this is occurring for all users, seems there are a large number of code reviews in your team. When you open the My work tab , the loading of the various code reviews cause a performance issue.
For this situation, you can try this workaroud: switch over to my code reviews in that Team Explorer drop down selector. After this, please double check whether the issue is gone or still exist.
Answering my own question here... My organisation ended up escalating this through Microsoft and eventually found that there was an issue with out of date statistics causing bad query plan generation. The query that was used to retrieve code review details was taking more than 60 seconds each time it was run.
The queries below will most likely make a significant different to performance if you encounter the same problem.
use <collection db name>;
UPDATE STATISTICS [dbo].[tbl_WorkItemCoreLatest] WITH FULLSCAN
use <collection db name>;
UPDATE STATISTICS [dbo].[tbl_WorkItemCustomLatest] WITH FULLSCAN
For reference, there's a duplicate of my original post on Microsoft Connect here: https://connect.microsoft.com/VisualStudio/Feedback/Details/3107261. The comments from Microsoft in this post indicate a number of people were seeing similar behaviour.
I just want to create report from Jira (Chart report showing total bugs of weekly report for 2 projects) I tried using time since report.Generated graph displayed total bugs for the 2 projects, But I want 2 projects name with each issues associated with project for each day.Is there any way to get the report?
I guess you are in search of a Dashboard. Dashboard will keep you update after regular interval about the status of the project. For creation of a dashboard you will need to create a filter first and then the Dashboard.
Create filter according to your requirements. i.e. search issues logged by QA in particular time period, in particular sprint etc.
This link will help you https://university.atlassian.com/uac/2.0/courses/end-user/jira/v60/search-and-filters/save-and-share-filter#/lesson-content-header
After creation of the Filter create a dashboard.
Follow steps mentioned in below link https://university.atlassian.com/uac/2.0/courses/end-user/jira/v60/dashboards/create-share-customize-a-dashboard
https://confluence.atlassian.com/display/JIRA/Customizing+the+Dashboard
Hope this helps you.
So, we have this one project which uses Cloud Storage and BigQuery as services. All has been well.
Then, I wanted to add Cloud SQL to this project to try it out. It asked for a unique Project ID so I gave it one. (The Project ID is different than the Project Number.)
Ever since then, I've been having a difficult time accessing my BigQuery tables. When I go to the BigQuery web interface, the URL contains the Project ID instead of the original Project Number. It shows the list of datasets, but now shows the Project Number before each dataset name and the datasets are greyed out and inaccessible. If I manually change the URL to contain the Project Number instead of the Project ID, it appears to work although it shows the list of datasets in the left nav twice, one set greyed out and inaccessible and the other set seemingly accessible.
At the same time, some code that I've been successfully using in Apps Script that accesses BigQuery is now regularly failing with a generic "We're sorry, a server error occurred. Please wait a bit and try again." I'm not sure if this is related to the Project ID/Project Number confusion, or if it's just a Red Herring.
Since we actively use the Cloud Storage service of this project, I am trying to be cautious with further experimentation with this project. I'm not sure if I should delete the Cloud SQL service in this project to get it back to the way it was, or if this is a known issue with some back-end solution. Please advise.
After setting the project id, there can be a delay where BigQuery picks up the change. It should happen within 15 minutes or so, but sometimes it takes longer.
If you send the project ID I can make sure it has been updated.