OpenTelemetry tracing for Forge apps

Forge Forge Platform and Tools
, ,
1

Atlassian already provides Forge app metrics. However, those metrics treat the app itself as a black box. As a developer/ops engineer it can be difficult to understand the black box without having a tool to see what’s going on inside.

Has Atlassian considered a solution that allows app developers to instrument app code and Atlassian to collect OpenTelemetry traces from apps to monitor performance issues within app executions?

2 Likes
2

Hello Tobias,

I’m a PM in the Forge ecosystem team. Could we connect on a call and get a better understanding of the issue you are facing and how the proposed feature would help? I’ll reach out and set something up.

1 Like
3

Hey @reddy1, thank you for your reply. Sure, I’m happy to connect and share more details.

4

I’m wondering if there are any updates or plans to support collecting/exporting OTEL traces in Forge functions. As long as I have to treat Forge functions as a black box, I hesitate to deploy code.

Some workarounds we explored:

  • host your own OTEL collector and send OTEL data directly there (the biggest challenge we found is securing the Connection from Forge to the collector)
  • log traces to the console

It would be nice if Forge functions had a locally running collector sidecar, and apps could simply export telemetry via the standard OTEL ports (localhost:4317 for gRPC or localhost:4318 for HTTP).

3 Likes
5

Hi @tbinna, I have created a Forge suggestion ticket for this - Jira

We will update the Jira ticket as we begin the explore phase.

2 Likes