Skip to content
This repository has been archived by the owner on May 25, 2022. It is now read-only.

Rename record to body #88

Merged
merged 5 commits into from
Apr 6, 2021
Merged

Conversation

lastchiliarch
Copy link
Contributor

Rename record to body, see #83 .

@djaglowski
Copy link
Member

I think we need to extend this to other usages of the term "Record". Particularly, anywhere users will see the term "record":

  • Documentation
  • Fields
    • RecordField / NewRecordField
    • $record syntax
  • Variable names, particularly in tests (inputRecord \ exptectedRecord)

@lastchiliarch
Copy link
Contributor Author

I think we need to extend this to other usages of the term "Record". Particularly, anywhere users will see the term "record":

  • Documentation

  • Fields

    • RecordField / NewRecordField
    • $record syntax
  • Variable names, particularly in tests (inputRecord \ exptectedRecord)

Thanks very much. Please remend me if anything is forgeted.

Copy link
Member

@djaglowski djaglowski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great. A few very minor suggestions.

It looks like there are a few more files to update.

> grep -Iris record .
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/operators/windows_eventlog_input.md:  "record": {
./docs/operators/k8s_event_input.md:  "record": {
./docs/operators/restructure.md:`value_expr` is an [expression](/docs/types/expression.md) with access to the `record` object
./docs/operators/restructure.md:<tr><td> Input record </td> <td> Output record </td></tr>
./docs/operators/restructure.md:The `remove` op removes a field from a record.
./docs/operators/restructure.md:<tr><td> Input record </td> <td> Output record </td></tr>
./docs/operators/restructure.md:<tr><td> Input record </td> <td> Output record </td></tr>
./docs/operators/restructure.md:<tr><td> Input record </td> <td> Output record </td></tr>
./docs/operators/restructure.md:<tr><td> Input record </td> <td> Output record </td></tr>

I omitted these lines from the above output, because I believe they use record in a different context and should be left as is:

./docs/operators/windows_eventlog_input.md:             "record_id": 1,
./operator/builtin/input/windows/subscription.go:               return EvtSubscribeStartAtOldestRecord
./operator/builtin/input/windows/xml.go:        RecordID    uint64      `xml:"System>EventRecordID"`
./operator/builtin/input/windows/xml.go:                "record_id":   e.RecordID,
./operator/builtin/input/windows/api.go:        // EvtSubscribeStartAtOldestRecord is a flag that will subscribe to all existing and future events.
./operator/builtin/input/windows/api.go:        EvtSubscribeStartAtOldestRecord uint32 = 2
./operator/builtin/input/windows/xml_test.go:           RecordID: 1,
./operator/builtin/input/windows/xml_test.go:           "record_id":   uint64(1),

| `start_at` | `end` | On first startup, where to start reading logs from the API. Options are `beginning` or `end` |
| `poll_interval` | 1s | The interval at which the channel is checked for new log entries. This check begins again after all new records have been read |
| `write_to` | $ | The record [field](/docs/types/field.md) written to when creating a new log entry |
| `poll_interval` | 1s | The interval at which the channel is checked for new log entries. This check begins again after all new body have been read |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| `poll_interval` | 1s | The interval at which the channel is checked for new log entries. This check begins again after all new body have been read |
| `poll_interval` | 1s | The interval at which the channel is checked for new log entries. This check begins again after all new bodies have been read |

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great. A few very minor suggestions.

It looks like there are a few more files to update.

> grep -Iris record .
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/types/severity.md:  "record": {
./docs/types/severity.md:  "record": {}
./docs/operators/windows_eventlog_input.md:  "record": {
./docs/operators/k8s_event_input.md:  "record": {
./docs/operators/restructure.md:`value_expr` is an [expression](/docs/types/expression.md) with access to the `record` object
./docs/operators/restructure.md:<tr><td> Input record </td> <td> Output record </td></tr>
./docs/operators/restructure.md:The `remove` op removes a field from a record.
./docs/operators/restructure.md:<tr><td> Input record </td> <td> Output record </td></tr>
./docs/operators/restructure.md:<tr><td> Input record </td> <td> Output record </td></tr>
./docs/operators/restructure.md:<tr><td> Input record </td> <td> Output record </td></tr>
./docs/operators/restructure.md:<tr><td> Input record </td> <td> Output record </td></tr>

I omitted these lines from the above output, because I believe they use record in a different context and should be left as is:

./docs/operators/windows_eventlog_input.md:             "record_id": 1,
./operator/builtin/input/windows/subscription.go:               return EvtSubscribeStartAtOldestRecord
./operator/builtin/input/windows/xml.go:        RecordID    uint64      `xml:"System>EventRecordID"`
./operator/builtin/input/windows/xml.go:                "record_id":   e.RecordID,
./operator/builtin/input/windows/api.go:        // EvtSubscribeStartAtOldestRecord is a flag that will subscribe to all existing and future events.
./operator/builtin/input/windows/api.go:        EvtSubscribeStartAtOldestRecord uint32 = 2
./operator/builtin/input/windows/xml_test.go:           RecordID: 1,
./operator/builtin/input/windows/xml_test.go:           "record_id":   uint64(1),

thanks a lot!

@@ -1,18 +1,18 @@
## Fields
##
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
##
## Fields

Copy link
Member

@djaglowski djaglowski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thank you @lastchiliarch for the contribution!

@djaglowski djaglowski merged commit 51eca70 into open-telemetry:main Apr 6, 2021
@lastchiliarch lastchiliarch deleted the issue83 branch April 7, 2021 02:37
tigrannajaryan pushed a commit to open-telemetry/opentelemetry-helm-charts that referenced this pull request Apr 14, 2021
Follows [#88 (opentelemetry-log-collection)](open-telemetry/opentelemetry-log-collection#88) and [#3017 (opentelemetry-collector-contrib)](open-telemetry/opentelemetry-collector-contrib#3017)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants