Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow apps to control logging used in getAgent / agent-proxy #1487

Open
kriswest opened this issue Jan 7, 2025 · 0 comments
Open

Allow apps to control logging used in getAgent / agent-proxy #1487

kriswest opened this issue Jan 7, 2025 · 0 comments
Labels

Comments

@kriswest
Copy link
Contributor

kriswest commented Jan 7, 2025

Enhancement Request

As discussed at meeting #1478, applications should be able to control what logging is exposed by getAgent and the agent-proxy (where getAgent has returned a DesktopAgentProxy linked to a browser-based DA) in the app's JavaScript console.

There are a number of different types of log statement currently, that should be individually controllable:

  • log-level connection messages from getAgent (default on)
  • debug level connection message from getAgent (default off)
  • debug-level logging from the DesktopAgentProxy (default off) - on all API calls message exchanges.
  • debug-level heartbeat messages from the DesktopAgentProxy (default off)

Error and warning messages should remain always logged.

@kriswest kriswest added enhancement New feature or request FDC3 for Web Browsers labels Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant