Hi guys,
is there currently a supported way for customers of a Forge app to access/consume the app’s logs or execution telemetry programmatically?
Our use case is background processing. We’d like customers to monitor whether the processing is succeeding/failing and ideally connect this to their own monitoring/alerting tools.
I see the App logs API and the newer observability capabilities (EAP), but these are mainly targeted at the app vendor/developer. Customers can also download logs manually from Admin Hub, but that’s not really suitable for operational monitoring.
So, can a customer programmatically access logs/telemetry for a Forge app installed on their site?
We can obviously implement our own monitoring in the app, but we’d prefer to use a native Forge/Atlassian capability if one exists.
Thank you.
We have the same problem: the Developer console UI for logs is clearly not on the level of SumoLogic/Datadog/ELK, but it’s also not too bad.
What customers get is way worse than that: a mere download button is not a good tool to troubleshoot problems.
Especially in the context of Runs on Atlassian apps, we don’t have a good place to store logs which would make them easily accessible: Forge SQL is expensive and has limited storage, KVS is not easily queryable and… tbh it’s not really meant to store logs.
Apps – AFAIK – can’t access their own logs at runtime, so there isn’t a good solution. If customers don’t enable log sharing, the only way to help them with support requests is to ask a dump of their logs and go through them manually.
No customer-side route exists to pull this programmatically.
The App Logs API and App Metrics API are scoped to the app owner or a contributor with log access, authenticated with the developer’s own API token. A customer admin cannot call either one for their own tenant. Admin Hub download is what customers get, and you already ruled that out for operational monitoring.
The EAP observability work runs on the same rails. Frontend logs, container metrics, all export under the app owner’s credentials.
Build it into the app. Write status somewhere the customer already has access. An issue property. A Confluence page. A webhook they subscribe to.
Writing logs to an issue property is unusable, good luck with doing search on that. Confluence is equally unusable.
Webhooks are not an option for Runs on Atlassian apps.
This is clearly an area where Forge is lacking, and it would be nice to see improvements or plans to improve it.