Is there any limit for retention of developer console logs?

Forge
1

I want to keep my developer console logs of my apps for at least one year.
Is it possible ?
Is there any limit (such as retention period or total log size) for developer console logs ?

2

Hi @ara,

Developer console logs are kept for only 60 days.

Note, logs are only available for the past 60 days and all dates are in UTC.

https://developer.atlassian.com/platform/forge/view-app-logs-and-installations/#filters

You might want to download logs regularly to keep your Forge logs for one year.

3

Hi @ara

Currently, developer console retains app logs for 60 days. This is not configurable.

We currently enforce a limit of 30 log lines per function invocation (see: https://developer.atlassian.com/platform/forge/platform-quotas-and-limits/#function-as-a-service-quotas)

Please let us know if you have any follow up questions.

Thanks,
Varun

4

Hi @varun, it would be great to have an API that allows us to download logs automatically and without the Forge CLI (which can’t filter by site and only returns logs for at most 20 invocations).

5

Hi @klaussner!

Would you please mind going a bit deeper into your use case? Assuming you have an API that allows you to filter log records per site for a given duration, how would you use it? (Where would you store it, how would you search for it etc…)

2 Likes
6

@varun I would use an API to make debugging/troubleshooting easier. At the moment, I prefer to download logs from the developer console and analyze them in an editor. It would be more convenient if I could just run a script that outputs the logs instead of opening the developer console in the browser, selecting a site and date range, and downloading and extracting the zip file. If the Forge CLI would allow us to filter logs by site and date range and output them in the same format as the logs downloaded from the developer console, that would also help.

There are also a few usability issues that make the developer console UI difficult to use:

  • The “Load more logs” button is located at the bottom of the page, but clicking it adds new logs at the top, so you have to constantly scroll up and down while looking for relevant logs.

  • Only a few logs are shown by default and I almost always have to click the “Load more logs” button multiple times to get enough logs.

  • To search for log metadata (site, module, etc.) using the browser’s page search, individual logs must be expanded.

  • JSON logs are not indented.

3 Likes
7

Hey @klaussner,

Thank you for your feedback around the CLI and your workflow.

Regarding a couple of points from the usability feedback

  1. You can try sort by date (change to descending) and click on load more logs. This will add more log lines to the bottom of the page.
  2. We show logs for 5 invocations currently. We may revisit this number. Is this number too low for your use case?

We’re working on improving dev console incrementally and will update the community when we deploy improvements to the end to end user experience. Please don’t hesitate to share any additional feedback and context around your use cases.

Regards,
Varun

1 Like
8

Hi, @varun!

You can try sort by date (change to descending) and click on load more logs. This will add more log lines to the bottom of the page.

Thanks! Sorting by date works much better. It would be nice if the console could remember the selected sort order after reloading the page.

We show logs for 5 invocations currently. We may revisit this number. Is this number too low for your use case?

I’m often looking at more logs/invocations when I’m debugging errors to get more context or to compare logs of different sites.