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

Log full data with delay #365

Merged
merged 5 commits into from
Sep 11, 2024
Merged

Log full data with delay #365

merged 5 commits into from
Sep 11, 2024

Conversation

Siegrift
Copy link
Collaborator

Closes #364

@Siegrift Siegrift requested a review from bdrhn9 September 10, 2024 11:48
@Siegrift Siegrift self-assigned this Sep 10, 2024
@Siegrift Siegrift changed the title Log delayed data Log full delayed data Sep 10, 2024
@Siegrift Siegrift changed the title Log full delayed data Log full data with delay Sep 10, 2024
PostSignedDataResponseSchema,
} from './types';
import { extractBearerToken, generateErrorResponse, isBatchUnique } from './utils';

const env = loadEnv();
const LOG_API_DATA_DELAY_MS = 5 * 60 * 1000;
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I think a hardcoded delay is good enough.

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes it looks okay unless we set delaySeconds to more than 5 minutes.

Copy link
Contributor

@bdrhn9 bdrhn9 left a comment

Choose a reason for hiding this comment

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

Looks good to me 👍🏼

PostSignedDataResponseSchema,
} from './types';
import { extractBearerToken, generateErrorResponse, isBatchUnique } from './utils';

const env = loadEnv();
const LOG_API_DATA_DELAY_MS = 5 * 60 * 1000;
Copy link
Contributor

Choose a reason for hiding this comment

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

Yes it looks okay unless we set delaySeconds to more than 5 minutes.

logged with the fields `airnode`, `encodedValue`, `templateId`, and `timestamp`. The `signature` field is intentionally
excluded for security reasons. Options:
logged with the fields `airnode`, `encodedValue`, `templateId`, `timestamp` and `signature`. The logging of this data is
delayed to make sure people with access to the logs won't be able to misuse the beacon data. Options:
Copy link
Contributor

Choose a reason for hiding this comment

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

Nit: maybe we can mention how much logging is delayed because it is already hard-coded to 5 minutes.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Sure.

@Siegrift
Copy link
Collaborator Author

Yes it looks okay unless we set delaySeconds to more than 5 minutes.

Yeah, but such data is practically unusable so I don't see us doing that.

@Siegrift Siegrift merged commit ad1188f into main Sep 11, 2024
4 checks passed
@Siegrift Siegrift deleted the log-delayed branch September 11, 2024 08:21
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.

Log full incoming signed data with delay
2 participants