Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Atlassian Statuspage Component Uptime

Planned
Jared Duquette User

With a statuspage, uptime is calculated via overrides. For example: 

 

 

In this example, we added another 5 minutes that is not reflected in the incident table: 

In order to get an accurate uptime% we can hit the /components/id/uptime endpoint with a certain time range: 

This matches the GUI. 

 

Please add a new uptime table that captures the 90 day uptime once per day and persists to the table. 

Please sign in to leave a comment.

Comments

3 comments

Date Votes
  • Official comment
    Sisan Kumar Sahu Fivetranner
    • Edited

    Hi Jared,

    Thank you for taking the time to walk us through the use case.

    We will begin working on this in our upcoming sprints. The request will first go through a feasibility assessment, and assuming everything proceeds as expected, we will move forward with implementing the endpoint.

    You can expect this to be completed before the end of March - potentially earlier. We are providing a conservative estimate to account for any unforeseen complexities that may arise during development.

    We will keep you updated as we make progress.

    Best regards,
    Sisan

  • Sisan Kumar Sahu Fivetranner
    • Edited

    Hi Jared,

    Thank you for your feature request regarding the Statuspage connector.

    We are actively monitoring customer demand to assess the feasibility of building and maintaining a high-quality Fivetran connector for this source. As we continue evaluating this opportunity, we’ll keep you informed of any updates or progress.

    In the meantime, it would be helpful to better understand your specific use case. Could you share what you’re looking to accomplish with the Statuspage connector? This context will help us prioritize appropriately and ensure we design the right solution.

    Thank you again for your feedback and support - it plays an important role in shaping our roadmap.

    Best regards,
    Sisan

  • Permanently deleted user User

    Thanks for the follow-up Sisan, 

    Use Case: we use statuspage to track uptime for critical dependencies (Tableau Online, Salesforce, internal services, etc.). Statuspage calculates uptime using manual overrides, for example, when an incident occurs, we add downtime that isn't automatically captured in the incident duration. 

    The current connector only syncs the incident table. This doesn't include the override data, so we can't calculate accurate uptime percentages from the replicated data. 

    The components/id/uptime endpoint returns the calculated uptime over a time range, which includes these overrides. THis matches what's displayed in the statuspage UI. 

    Straightforward API replication, end point is already documented and stable.