mirror of
https://github.com/NarrativeScience-old/log.io.git
synced 2026-04-26 09:35:53 +03:00
[GH-ISSUE #202] Mask Log Data #169
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/log.io-NarrativeScience-old#169
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @astutesoftware on GitHub (Nov 24, 2018).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/202
What would be an ideal approach that a log that is being streamed has a middle layer or mechanism to mask some of the sensitive data.
I have a use case where support personnel need to track logs looking for sms delivery to a particular recipient by phone number but the log contains more than required sensitive data.
Ideally this case would require a middleware which can reside at the server end and masks the data before streaming or be embedded at the client end (browser)
any thoughts?
@msmathers commented on GitHub (Jan 12, 2020):
There are currently no plans for middleware support... I'd recommend writing a separate process that reads the raw log files with sensitive data and outputs new, sanitized log files. Then point log.io at the sanitized files.