-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[DOCS-9171] Add unresolvable behavior template syntax #27299
Open
maycmlee
wants to merge
2
commits into
may/2024-q4-obs-pipelines
Choose a base branch
from
may/add-unresolvable-behavior-template-syntax
base: may/2024-q4-obs-pipelines
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
[DOCS-9171] Add unresolvable behavior template syntax #27299
maycmlee
wants to merge
2
commits into
may/2024-q4-obs-pipelines
from
may/add-unresolvable-behavior-template-syntax
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1 task
Preview links (active after the
|
neko-dd
reviewed
Jan 24, 2025
Comment on lines
+49
to
+57
| ----------------- | -------------------------------------| -----------------------------------------------------------------------------------------------| | ||
| Amazon Opensearch | Index | The Worker creates an index named `datadog-op` and sends the logs there. | | ||
| Amazon S3 | Prefix | The Worker creates a folder named `OP_UNRESOLVED_TEMPLATE_LOGS/` and publishes the logs there. | | ||
| Azure Blob | Prefix | The Worker creates a folder named `OP_UNRESOLVED_TEMPLATE_LOGS/` and publishes the logs there. | | ||
| Elasticsearch | Source type | The Worker creates an index named `datadog-op` and sends the logs there. | | ||
| Google Chronicle | Log type | Defaults to `vector_dev` log type. | | ||
| Google Cloud | Prefix | The Worker creates a folder named `OP_UNRESOLVED_TEMPLATE_LOGS/` and publishes the logs there. | | ||
| Opensearch | Index | The Worker creates an index named `datadog-op` and sends the logs there. | | ||
| Splunk HEC | Index<br>Source type | The Worker publishes the logs to the default index configured in Splunk. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do "send" and "publish" have two different meanings in this case?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yeah, meant to ask eng about that. Asking now.
Co-authored-by: Sandra (neko) <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Adds info about unresolvable behavior for templated fields.
Child PR of: #26921
Merge instructions
Merge readiness:
Merge queue is enabled in this repo. To have it automatically merged after it receives the required reviews, create the PR (from a branch that follows the
<yourname>/description
naming convention) and then add the following PR comment:Additional notes