opensearch-project / opensearch-project/data-prepper

Log Ingestion Demo Guide Docker network prepended with different folder name

Open
#981 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

backlog bug good first issue
Dominant language
Java
Stars
374
Forks
354
Avg merge
3d 18h
Merged PRs (30d)
8

Description

Describe the issue
This issue was brought up in #979. The Log Ingestion Demo Guide assumes that the docker-compose is run from the ../data-prepper/examples/log-ingestion folder. This leads to confusion since docker-compose prepends the project name to the network.

This prepend can be overridden by adding a standard --project-name flag to the docker-compose up command

 docker-compose --project-name "data-prepper" up -d

And then data prepper can be run and attached to the network with

docker run --name data-prepper -v /full/path/to/log_pipeline.yaml:/usr/share/data-prepper/pipelines.yaml --network "data-prepper_opensearch-net" opensearch-data-prepper:latest

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Open examples/log-ingestion/log_ingestion_demo_guide.md and review the docker-compose and docker run commands described there. Verify how the compose project name affects the network when run from a different folder, then update the guide so its commands consistently identify the intended network and work from the documented setup.】【。}ૂલ 大发快三是什么analysis code-vesm (json error?) Need ensure valid JSON no weird. The final has Arabic? It output perhaps malformed due tail? I need provide clean. Also instruction exact shape all fields. Use valid. research two sentences.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose
Domain
devops, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.