Skip to content

test: synchronizing gherkin spec #1490

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

Merged
merged 1 commit into from
Mar 16, 2022
Merged

test: synchronizing gherkin spec #1490

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
246 changes: 246 additions & 0 deletions tests/bdd/features/otel_bridge.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,246 @@
@opentelemetry-bridge
Feature: OpenTelemetry bridge

# --- Creating Elastic span or transaction from OTel span

Scenario: Create transaction from OTel span with remote context
Given an agent
And OTel span is created with remote context as parent
Then Elastic bridged object is a transaction
Then Elastic bridged transaction has remote context as parent

Scenario: Create root transaction from OTel span without parent
Given an agent
And OTel span is created without parent
And OTel span ends
Then Elastic bridged object is a transaction
Then Elastic bridged transaction is a root transaction
# outcome should not be inferred from the lack/presence of errors
Then Elastic bridged transaction outcome is "unknown"

Scenario: Create span from OTel span
Given an agent
And OTel span is created with local context as parent
And OTel span ends
Then Elastic bridged object is a span
Then Elastic bridged span has local context as parent
# outcome should not be inferred from the lack/presence of errors
Then Elastic bridged span outcome is "unknown"

# --- OTel span kind mapping for spans & transactions

Scenario Outline: OTel span kind <kind> for spans & default span type & subtype
Given an agent
And an active transaction
And OTel span is created with kind "<kind>"
And OTel span ends
Then Elastic bridged object is a span
Then Elastic bridged span OTel kind is "<kind>"
Then Elastic bridged span type is "<default_type>"
Then Elastic bridged span subtype is "<default_subtype>"
Examples:
| kind | default_type | default_subtype |
| INTERNAL | app | internal |
| SERVER | unknown | |
| CLIENT | unknown | |
| PRODUCER | unknown | |
| CONSUMER | unknown | |

Scenario Outline: OTel span kind <kind> for transactions & default transaction type
Given an agent
And OTel span is created with kind "<kind>"
And OTel span ends
Then Elastic bridged object is a transaction
Then Elastic bridged transaction OTel kind is "<kind>"
Then Elastic bridged transaction type is 'unknown'
Examples:
| kind |
| INTERNAL |
| SERVER |
| CLIENT |
| PRODUCER |
| CONSUMER |

# OTel span status mapping for spans & transactions

Scenario Outline: OTel span mapping with status <status> for transactions
Given an agent
And OTel span is created with kind 'SERVER'
And OTel span status set to "<status>"
And OTel span ends
Then Elastic bridged object is a transaction
Then Elastic bridged transaction outcome is "<outcome>"
Examples:
| status | outcome |
| unset | unknown |
| ok | success |
| error | failure |

Scenario Outline: OTel span mapping with status <status> for spans
Given an agent
Given an active transaction
And OTel span is created with kind 'INTERNAL'
And OTel span status set to "<status>"
And OTel span ends
Then Elastic bridged object is a span
Then Elastic bridged span outcome is "<outcome>"
Examples:
| status | outcome |
| unset | unknown |
| ok | success |
| error | failure |

# --- span type, subtype and action inference from OTel attributes

# --- HTTP server
# https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/http.md#http-server
Scenario Outline: HTTP server [ <http.url> <http.scheme> ]
Given an agent
And OTel span is created with kind 'SERVER'
And OTel span has following attributes
| http.url | <http.url> |
| http.scheme | <http.scheme> |
And OTel span ends
Then Elastic bridged object is a transaction
Then Elastic bridged transaction type is "request"
Examples:
| http.url | http.scheme |
| http://testing.invalid/ | |
| | http |

# --- HTTP client
# https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/http.md#http-client
Scenario Outline: HTTP client [ <http.url> <http.scheme> <http.host> <net.peer.ip> <net.peer.name> <net.peer.port> ]
Given an agent
And an active transaction
And OTel span is created with kind 'CLIENT'
And OTel span has following attributes
| http.url | <http.url> |
| http.scheme | <http.scheme> |
| http.host | <http.host> |
| net.peer.ip | <net.peer.ip> |
| net.peer.name | <net.peer.name> |
| net.peer.port | <net.peer.port> |
And OTel span ends
Then Elastic bridged span type is 'external'
Then Elastic bridged span subtype is 'http'
Then Elastic bridged span OTel attributes are copied as-is
Then Elastic bridged span destination resource is set to "<resource>"
Examples:
| http.url | http.scheme | http.host | net.peer.ip | net.peer.name | net.peer.port | resource |
| https://testing.invalid:8443/ | | | | | | testing.invalid:8443 |
| https://[::1]/ | | | | | | [::1]:443 |
| http://testing.invalid/ | | | | | | testing.invalid:80 |
| | http | testing.invalid | | | | testing.invalid:80 |
| | https | testing.invalid | 127.0.0.1 | | | testing.invalid:443 |
| | http | | 127.0.0.1 | | 81 | 127.0.0.1:81 |
| | https | | 127.0.0.1 | | 445 | 127.0.0.1:445 |
| | http | | 127.0.0.1 | host1 | 445 | host1:445 |
| | https | | 127.0.0.1 | host2 | 445 | host2:445 |

# --- DB client
# https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/database.md
Scenario Outline: DB client [ <db.system> <net.peer.ip> <net.peer.name> <net.peer.port>]
Given an agent
And an active transaction
And OTel span is created with kind 'CLIENT'
And OTel span has following attributes
| db.system | <db.system> |
| db.name | <db.name> |
| net.peer.ip | <net.peer.ip> |
| net.peer.name | <net.peer.name> |
| net.peer.port | <net.peer.port> |
And OTel span ends
Then Elastic bridged span type is 'db'
Then Elastic bridged span subtype is "<db.system>"
Then Elastic bridged span OTel attributes are copied as-is
Then Elastic bridged span destination resource is set to "<resource>"
Examples:
| db.system | db.name | net.peer.ip | net.peer.name | net.peer.port | resource |
| mysql | | | | | mysql |
| oracle | | | oracledb | | oracledb |
| oracle | | 127.0.0.1 | | | 127.0.0.1 |
| mysql | | 127.0.0.1 | dbserver | 3307 | dbserver:3307 |
| mysql | myDb | | | | mysql/myDb |
| oracle | myDb | | oracledb | | oracledb/myDb |
| oracle | myDb | 127.0.0.1 | | | 127.0.0.1/myDb |
| mysql | myDb | 127.0.0.1 | dbserver | 3307 | dbserver:3307/myDb |

# --- Messaging consumer (transaction consuming/receiving a message)
# https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/messaging.md
Scenario: Messaging consumer
Given an agent
And an active transaction
And OTel span is created with kind 'CONSUMER'
And OTel span has following attributes
| messaging.system | anything |
And OTel span ends
Then Elastic bridged transaction type is 'messaging'

# --- Messaging producer (client span emitting a message)
# https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/messaging.md
Scenario Outline: Messaging producer [ <messaging.system> <messaging.destination> <messaging.url> <net.peer.ip> <net.peer.name> <net.peer.port>]
Given an agent
And an active transaction
And OTel span is created with kind 'PRODUCER'
And OTel span has following attributes
| messaging.system | <messaging.system> |
| messaging.destination | <messaging.destination> |
| messaging.url | <messaging.url> |
| net.peer.ip | <net.peer.ip> |
| net.peer.name | <net.peer.name> |
| net.peer.port | <net.peer.port> |
And OTel span ends
Then Elastic bridged span type is 'messaging'
Then Elastic bridged span subtype is "<messaging.system>"
Then Elastic bridged span OTel attributes are copied as-is
Then Elastic bridged span destination resource is set to "<resource>"
Examples:
| messaging.system | messaging.destination | messaging.url | net.peer.ip | net.peer.name | net.peer.port | resource |
| rabbitmq | | amqp://carrot:4444/q1 | | | | carrot:4444 |
| rabbitmq | | | 127.0.0.1 | carrot-server | 7777 | carrot-server:7777 |
| rabbitmq | | | | carrot-server | | carrot-server |
| rabbitmq | | | 127.0.0.1 | | | 127.0.0.1 |
| rabbitmq | myQueue | amqp://carrot:4444/q1 | | | | carrot:4444/myQueue |
| rabbitmq | myQueue | | 127.0.0.1 | carrot-server | 7777 | carrot-server:7777/myQueue |
| rabbitmq | myQueue | | | carrot-server | | carrot-server/myQueue |
| rabbitmq | myQueue | | 127.0.0.1 | | | 127.0.0.1/myQueue |

# --- RPC client
# https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/rpc.md
Scenario Outline: RPC client [ <rpc.system> <rpc.service> <net.peer.ip> <net.peer.name> <net.peer.port>]
Given an agent
And an active transaction
And OTel span is created with kind 'CLIENT'
And OTel span has following attributes
| rpc.system | <rpc.system> |
| rpc.service | <rpc.service> |
| net.peer.ip | <net.peer.ip> |
| net.peer.name | <net.peer.name> |
| net.peer.port | <net.peer.port> |
And OTel span ends
Then Elastic bridged span type is 'external'
Then Elastic bridged span subtype is "<rpc.system>"
Then Elastic bridged span OTel attributes are copied as-is
Then Elastic bridged span destination resource is set to "<resource>"
Examples:
| rpc.system | rpc.service | net.peer.ip | net.peer.name | net.peer.port | resource |
| grpc | | | | | grpc |
| grpc | myService | | | | grpc/myService |
| grpc | myService | | rpc-server | | rpc-server/myService |
| grpc | myService | 127.0.0.1 | rpc-server | | rpc-server/myService |
| grpc | | 127.0.0.1 | rpc-server | 7777 | rpc-server:7777 |
| grpc | myService | 127.0.0.1 | rpc-server | 7777 | rpc-server:7777/myService |
| grpc | myService | 127.0.0.1 | | 7777 | 127.0.0.1:7777/myService |

# --- RPC server
# https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/rpc.md
Scenario: RPC server
Given an agent
And OTel span is created with kind 'SERVER'
And OTel span has following attributes
| rpc.system | grpc |
And OTel span ends
Then Elastic bridged transaction type is 'request'