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

RUMM-101 Create SDK project #2

Merged
merged 5 commits into from
Dec 11, 2019
Merged

Conversation

ncreated
Copy link
Member

This PR introduces basic project setup. It consist of:

  • Package.swift that describes SDK project structure (naming and files location).
  • custom kickoff.sh shell script meant to be run right after git clone to set up project for contributions. Currently it only generates Xcode project and installs Datadog's code templates, but more things will come in the future.

@ncreated ncreated self-assigned this Dec 10, 2019
Copy link
Member

@xgouchet xgouchet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not an iOS expert, but this looks quite good :)

Copy link
Contributor

@iGranDav iGranDav left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I love the DataDog template idea 👍🏼 We could share it

Tests/DatadogTests/DatadogTests.swift Show resolved Hide resolved
Package.swift Show resolved Hide resolved
@ncreated ncreated merged commit b23c25b into master Dec 11, 2019
@ncreated ncreated deleted the ncreated/RUMM-101-create-sdk-project branch December 11, 2019 07:41
buranmert added a commit that referenced this pull request Jul 27, 2020
We observe non-parseable logs sent to intake
In a certain org which has high volumes of logs,
%0.3-0.5 of all logs are not parsed properly in dashboard

Hypothesis #1
Data being read is malformed, because every malformed log has their malformed part at the very end
So if we can read the file later, we can have valid payload
This commit implements this hypothesis

Hypothesis #2
Write op corrupts the file and we need to watch write ops closely so that we can catch and recover errors
This requires major refactoring in File.swift and related files
buranmert added a commit that referenced this pull request Jul 27, 2020
We observe non-parseable logs sent to intake
In a certain org which has high volumes of logs,
%0.3-0.5 of all logs are not parsed properly in dashboard

Hypothesis #1
Data being read is malformed, because every malformed log has their malformed part at the very end
So if we can read the file later, we can have valid payload
This commit implements this hypothesis

Hypothesis #2
Write op corrupts the file and we need to watch write ops closely so that we can catch and recover errors
This requires major refactoring in File.swift and related files
@buranmert buranmert mentioned this pull request Sep 4, 2020
2 tasks
buranmert added a commit that referenced this pull request Jun 25, 2021
alai97 added a commit that referenced this pull request Sep 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants