Clarification on Forge pricing & log usage

Hi,

Agile Hive Cloud runs completely on Atlassian and we are facing the detail, that logging seems more expensive than computation? That’s blatantly insane. No platform has that high costs for logging.

The more logs the easier we can help customers during runtime on their site. We already keep it compact and don’t log in loops in example, only after loops. Still we are facing a lot of logging to debug the application in case of incidents. Especially when running into error codes from Atlassian APIs, which happens frequently. So a lot of errors from third parties like Atlassian API lead to lots of logs that result in costs. That does not make sense in order to deliver a reliable monitoring.

On top of that we can only access logs for 2 weeks in the past on the Forge console now? What costs so much? We get almost nothing out of it. 1GB is nothing on large customer sites with frequent usage of 100k users and millions of issue edits every month. I prefer to push the logging into our own tooling in GCP which is way cheaper and gives us more insight and statistics per site and alerting. The current log system is errors prone, often fails like last week where we got no logs but still charges for processing logs? And the limits are very low. It’s almost impossible to help large enterprise sites because the there are no log statistics over time. We cannot keep track if measurements in our app work out.

I am looking into pushing everything into our monitoring in GCP and hope that it can be even easier in the future. And why does that also result in costs? Can logging into a remote sink happen more direct?

Kind Regards

5 Likes