Data Lag in Atlassian Analytics
Incident
Report for Atlassian Analytics
Resolved
We have completed verification of the data refresh for the jira_issue and jira_status_history tables. All data inconsistency issues are resolved and we are closing the incident.
Update
We have completed a refresh of data into the lake across all regions. The next step is to verify this refresh resolved data inconsistencies in the jira_issue and jira_status_history tables. We will provide our next update once the verification is complete.
Update
Most of the data has been recovered in all regions for all entities and customers. We continue to monitor the Data Lake for a bit longer before closing this incident
Update
Most of the data has been recovered in all regions for all entities and customers. We continue to monitor the Data Lake for a bit longer before closing this incident
Update
We are continuing to monitor the progress of the data refresh into the Atlassian Data Lake. The majority of data has already been refreshed, however, there are still some jobs outstanding specifically for a few customers. We will post the next update in 24 hours.
Update
We are continuing to monitor the progress of the data refresh into the Atlassian Data Lake. The majority of data has already been refreshed, however, there are still some jobs outstanding specifically for a few customers. We will post the next update in 24 hours.
Update
We are continuing to monitor the progress of the data refresh into the Atlassian Data Lake. The majority of data has already been refreshed, however, there are still some jobs outstanding specifically for a few customers. We will post the next update in 12 hours.
Update
We are continuing to monitor the progress of the data refresh into the Atlassian Data Lake. The majority of data has already been refreshed, however, there are still some jobs outstanding specifically for a few customers. We will post the next update in 12 hours.
Update
We identified the root cause and applied a fix. There are a few selected workspaces which are yet to be refreshed. We are continuing to monitor the progress of the data refresh into the Atlassian Data Lake. The majority of data has already been refreshed, however, there are still some jobs outstanding specifically for a few customers. We will post the next update in 12 hours.
Update
We are continuing to monitor progress of the Jira data refresh into the Atlassian Data Lake and are also investigating into performance improvements to speed up the process. The majority of data has already been refreshed, however there are still some jobs outstanding specifically for customers in a single region. We will post the next update in 6 hours.
Update
We are continuing to monitor progress of the Jira data refresh into the Atlassian Data Lake. The majority of data has already been refreshed, however there are still some jobs outstanding specifically for customers in a single region. We will post the next update within 4 hours.
Update
We are continuing to monitor progress of the Jira data refresh into the Atlassian Data Lake. The majority of data has already been refreshed, however there are still some jobs outstanding specifically for customers in a single region. We will post the next update within 4 hours.
Update
We are continuing to monitor progress of the Jira data refresh into the Atlassian Data Lake. The majority of data has already been refreshed, however there are still some jobs outstanding. We will post the next update within 4 hours.
Update
Jira refresh is complete for a few regions . We continue to monitor the progress of the job and will provide further updates once its available
Update
The data refresh for confluence is complete . The Jira refresh is still underway and will take a few hours to catch up .
Monitoring
The data refresh is running and is being monitored .
Update
We are continuing to investigate this issue.
Investigating
Data is currently being refreshed across confluence and Jira issue to fix data inconsistencies .Data lag is expected during this time . We will provide more updates once the data refresh is complete and the lag is back to expected range.
This incident affected: Dashboards and Atlassian Data Lake.