feat: add vector with defaults

[Ian2012]

Description

This PR adds Vector as a dependency and sets defaults for:

• Extracting application logs (lms, cms, ingress, cert-manager, etc)
• Extracting tracking logs from Open edX.
• Storing compressed tracking logs in gzip files on an S3-like storage (can be tweaked to work with Cloudwatch, Minio, etc) by date.

Closes: #32

[openedx-webhooks]

Thanks for the pull request, @Ian2012!

What's next?

Please work through the following steps to get your changes ready for engineering review:

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

🔘 Let us know that your PR is ready for review:

Who will review my changes?

This repository is currently maintained by @openedx/openedx-k8s-harmony-maintainers. Tag them in a comment and let them know that your changes are ready for review.

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[Ian2012]

@pomegranited @bmtcril You may be interested as well on this PR

[bmtcril]

How is this going to work with the existing Aspects vector settings? Are the two going to be exclusive?

[Ian2012]

Yes, both need to be exclusive, for resource consumption and pipeline tracking. However, another filter and a sink can be added to filter specifics of any namespace.

However, keep in mind that Ralph is the recommended pipeline to use.

I can leave examples for it

[bmtcril]

Ok, when this merges you should also update these docs:
https://docs.openedx.org/projects/openedx-aspects/en/latest/technical_documentation/how-tos/production_configuration.html#vector
https://docs.openedx.org/projects/openedx-aspects/en/latest/technical_documentation/quickstarts/vector.html

[Ian2012]

I've implemented a ClickHouse filter and sink example. Assuming there are multiple OpenedX installations in the same cluster, a filter, a transformer, and a sink must be implemented per namespace.

Basically what we do is:

• Get all logs from a specific namespace (filter)
• Get all xapi_tracking logs. (transformer)
• Sink them to the specific ClickHouse instance/cluster. (sink)

[gabor-boros]

@Ian2012 Can you please give an example for multiple instance per cluster configuration setup in the https://github.com/openedx/openedx-k8s-harmony/blob/main/values-example.yaml?

[Ian2012]

I've updated the values-example.yaml with the elements for one installation filtered by namespace. It just needs to be replicated for every openedx namespace with Aspects installed.

[Ian2012]

I've updated the default values as the sinks cannot be disabled, they need to be removed. Examples were added to setup CloudWatch and S3 sinks. This was tested on a production environment with CloudWatch, S3, and VictoriaLogs sinks, everything worked well and logs for the lms|cms are grouped when there are exceptions.