Skip to content

Incident detail

Daily consumption report is not showing current usage data

Resolved incidentMinor1 affected service

Timeline window

to

Get alerted the next time Cloudera breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Identified

    The daily consumption report that is available on the Cloudera Management Console has not been reporting current usage data since Thu Jun 19th 2025.

    Our teams have identified the source of the issue and are working on implementing a solution to make the data available by this Friday Jun 27th 2025, if not sooner.

    While the team is working on resolving the issue customers may use https://my.cloudera.com/account/usage to avail their consumption reports.

  2. Monitoring

    Our teams have successfully deployed the fix. The data pipeline is running, and data up to 21st June is available. The backlog in consumption reporting data will be processed gradually.

    Meanwhile, customers may use https://my.cloudera.com/account/usage to get the consumption reports.

    Our teams are actively monitoring the situation.

  3. Resolved

    Our teams have confirmed that the issue has been resolved. The data pipelines have now caught up on the backlogged consumption reporting data.

    If you are still experiencing issues or have any questions, please raise a support case with us.

    A root cause analysis (RCA) will be published within seven business days.

  4. Resolved

    On 23rd of June, we were notified that our Consumption Dashboards were not displaying current usage data from June 19th, 2024.

    Upon further investigation, we identified that the pipeline that ingests data into consumption was not progressing due to out-of-memory crash errors. The issue was caught and fixed, but the catch-up of the pipeline caused a delay of 2-3 days.

    While the reprocessing was happening in the background, customers could still use https://my.cloudera.com/account/usage to get the same consumption reports.

    Our teams have instituted preemptive measures and refined our internal protocols to manage similar incidents proactively in the future.

    We apologize for any inconvenience this may have caused and remain committed to implementing all necessary measures to prevent the recurrence of such issues.

Keep exploring

More from Cloudera

Neighboring incidents on Cloudera's timeline and the rest of their record on OutageDeck.