Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Integration for aws-alb on top of S3 using Materialized view #1496

Draft
wants to merge 22 commits into
base: main
Choose a base branch
from
Draft

Integration for aws-alb on top of S3 using Materialized view #1496

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
22 commits
Select commit Hold shift + click to select a range
b9d42bf
Integration for aws.alb -> s3 -> MaterializedView using opensearch SQ…
YANG-DB Apr 5, 2023
c152f90
fix broken markdown documents links and remove redundant docs (#1495)
YANG-DB Apr 5, 2023
c13f7a6
add additional information of the steps and assets dependencies with …
YANG-DB Apr 5, 2023
3af084e
Merge remote-tracking branch 'origin/aws_alb_integration' into aws_al…
YANG-DB Apr 13, 2023
46a0f2b
add diagrams for the data flow
YANG-DB Apr 13, 2023
b5050d8
Merge remote-tracking branch 'origin/aws_alb_integration' into aws_al…
YANG-DB Apr 13, 2023
8bdf6d4
add diagram for the flow manager to load the assets of the integration
YANG-DB Apr 13, 2023
3c1ba96
Merge remote-tracking branch 'origin/aws_alb_integration' into aws_al…
YANG-DB Apr 14, 2023
25d8cb8
update sample document fields references
YANG-DB Apr 14, 2023
4e6cee1
Merge remote-tracking branch 'origin/aws_alb_integration' into aws_al…
YANG-DB Apr 14, 2023
13166ab
update reference fields references
YANG-DB Apr 14, 2023
7674a3a
Merge remote-tracking branch 'origin/aws_alb_integration' into aws_al…
YANG-DB Apr 14, 2023
da20c62
add connectivity flow diagram
YANG-DB Apr 14, 2023
8b94fcb
Merge remote-tracking branch 'origin/aws_alb_integration' into aws_al…
YANG-DB Apr 14, 2023
4b43e17
move alb into a distinct aws folder
YANG-DB Apr 14, 2023
2fc3fc0
Merge remote-tracking branch 'origin/aws_alb_integration' into aws_al…
YANG-DB Apr 19, 2023
e8a9ceb
add fields.md support for spec and details
YANG-DB Apr 19, 2023
311a58f
Merge remote-tracking branch 'origin/aws_alb_integration' into aws_al…
YANG-DB Apr 20, 2023
3689a46
add dashboard preview images
YANG-DB Apr 20, 2023
c0002f3
Merge branch 'main' into aws_alb_integration
YANG-DB May 3, 2023
a1180ee
Merge branch 'main' into aws_alb_integration
YANG-DB May 3, 2023
7cdad55
append service & traces analytics docs & info
YANG-DB May 18, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/schema/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,7 +105,7 @@ For example the [`logs.schema`](../../src/main/resources/schema/observability/lo
...
```

We can observe that the `traceId` field is defined by referencing to the [Span](../../src/main/resources/schema/observability/traces/traceGroups.schema) schema and explicitly to the `#/properties/spanId` field reference location.
We can observe that the `traceId` field is defined by referencing to the [Span](../../src/main/resources/schema/observability/traces/tracegroups.schema) schema and explicitly to the `#/properties/spanId` field reference location.

### Mapping related
Each mapping template will contain the foreign schemas that are referenced to in that specific mapping file. For example the [`logs.mapping`](../../src/main/resources/schema/observability/logs/logs.schema) file will contain the next correlation object in the mapping `_meta` section:
Expand Down
6 changes: 3 additions & 3 deletions docs/schema/observability/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ For example the [`logs.schema`](../../../src/main/resources/schema/observability
...
```

We can observe that the `traceId` field is defined by referencing to the [Span](../../../src/main/resources/schema/observability/traces/traceGroups.schema) schema and explicitly to the `#/properties/spanId` field reference location.
We can observe that the `traceId` field is defined by referencing to the [Span](../../../src/main/resources/schema/observability/traces/tracegroups.schema) schema and explicitly to the `#/properties/spanId` field reference location.

### Mapping related
Each mapping template will contain the foreign schemas that are referenced to in that specific mapping file. For example the [`logs.mapping`](../../../src/main/resources/schema/observability/logs/logs.schema) file will contain the next correlation object in the mapping `_meta` section:
Expand Down Expand Up @@ -172,7 +172,7 @@ The correlation metadata info is exported in the following way:

### Schema related
In JSON Schema, there is no built-in way to represent relationships directly between multiple schemas, like you would find in a relational database. However, you can establish relationships indirectly by using a combination of `$id`, `$ref`, and consistent property naming across your schemas.
For example the [`logs.schema`](../../../src/main/resources/schema/observability/logs/logs.schema) file contains the next `$ref` references for the `traceId` & `spanId` fields that belong to the [`traces.schema`](../../../src/main/resources/schema/observability/traces/traceGroups.schema).
For example the [`logs.schema`](../../../src/main/resources/schema/observability/logs/logs.schema) file contains the next `$ref` references for the `traceId` & `spanId` fields that belong to the [`traces.schema`](../../../src/main/resources/schema/observability/traces/tracegroups.schema).

```json5
...
Expand All @@ -185,7 +185,7 @@ For example the [`logs.schema`](../../../src/main/resources/schema/observability
...
```

We can observe that the `traceId` field is defined by referencing to the [Span](../../../src/main/resources/schema/observability/traces/traceGroups.schema) schema and explicitly to the `#/properties/spanId` field reference location.
We can observe that the `traceId` field is defined by referencing to the [Span](../../../src/main/resources/schema/observability/traces/tracegroups.schema) schema and explicitly to the `#/properties/spanId` field reference location.

### Mapping related
Each mapping template will contain the foreign schemas that are referenced to in that specific mapping file. For example the [`logs.mapping`](../../../src/main/resources/schema/observability/logs/logs.mapping) file will contain the next correlation object in the mapping `_meta` section:
Expand Down
2 changes: 1 addition & 1 deletion docs/schema/observability/traces/Usage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ Start the OpenSearch cluster and follow the next steps for manually setup of the

`>> PUT _component_template/tracegroups_template`

Copy the [traceGroups.mapping](../../../../src/main/resources/schema/observability/traces/traceGroups.mapping)
Copy the [traceGroups.mapping](../../../../src/main/resources/schema/observability/traces/tracegroups.mapping)

`>> PUT _index_template/traces`

Expand Down
Loading