newrelic / newrelic/aws_s3_log_ingestion_lambda
NewRelic importing logs from S3 bucket/folder_name path
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Description
We are creating data partitions from an S3 bucket which contains logfiles for several components in a stack.
We’d like to write query like this → entityName = ‘S3BucketName/folder_name’ so that we can segregate the data at the time of creation of a data partition without having to apply filters afterwards.
Or at least, create an attribute (folder_name) for the path, so that the filtering is more efficient than searching through text.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the AWS Lambda reads S3 object paths and creates New Relic data partitions. Compare the requested entityName format with the alternative of exposing folder_name as an attribute, then identify the existing ingestion tests or entry points that cover partition metadata. Done means component folders can be segregated at partition creation without text filtering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- cloud, data, observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100