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

Create a package for parsing logs #510

Closed
lawrence-forooghian opened this issue Dec 12, 2022 · 1 comment · Fixed by #511
Closed

Create a package for parsing logs #510

lawrence-forooghian opened this issue Dec 12, 2022 · 1 comment · Fixed by #511
Assignees
Labels
code-quality Affects the developer experience when working in our codebase.

Comments

@lawrence-forooghian
Copy link
Collaborator

This will be useful for any tasks in which we want to analyse logs emitted by the library, for example answering this question.

I want to create a library that will allow us to build scripts/tooling in Swift for analysing the logs emitted by the library and the example apps. It should parse a log file and turn it into an array of structs representing a line (with information like timestamp, log level, etc).

@sync-by-unito
Copy link

sync-by-unito bot commented Dec 12, 2022

➤ Automation for Jira commented:

The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-3177

@lawrence-forooghian lawrence-forooghian self-assigned this Dec 12, 2022
@lawrence-forooghian lawrence-forooghian added the code-quality Affects the developer experience when working in our codebase. label Dec 12, 2022
lawrence-forooghian added a commit that referenced this issue Dec 12, 2022
This just copies the logging code from the publisher example app to the
subscriber one. Means that we get the same format and hence will be able
to use the same code for parsing their output in #510.
lawrence-forooghian added a commit that referenced this issue Dec 12, 2022
This just copies the logging code from the publisher example app to the
subscriber one. Means that we get the same format and hence will be able
to use the same code for parsing their output in #510.
lawrence-forooghian added a commit that referenced this issue Dec 13, 2022
This just copies the logging code from the publisher example app to the
subscriber one. Means that we get the same format and hence will be able
to use the same code for parsing their output in #510.
lawrence-forooghian added a commit that referenced this issue Dec 13, 2022
This just copies the logging code from the publisher example app to the
subscriber one. Means that we get the same format and hence will be able
to use the same code for parsing their output in #510.
lawrence-forooghian added a commit that referenced this issue Dec 13, 2022
This just copies the logging code from the publisher example app to the
subscriber one. Means that we get the same format and hence will be able
to use the same code for parsing their output in #510.
lawrence-forooghian added a commit that referenced this issue Dec 13, 2022
This just copies the logging code from the publisher example app to the
subscriber one. Means that we get the same format and hence will be able
to use the same code for parsing their output in #510.
@sync-by-unito sync-by-unito bot reopened this Feb 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code-quality Affects the developer experience when working in our codebase.
Development

Successfully merging a pull request may close this issue.

2 participants