Monitoring main documentation #3050
Open
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
Update monitoring.md
Update spryker-monitoring-integration.md
removed duplicated text
…tion Added overview of OTEL
added details of OTel integration
added md extension
added md extension
minor changes
minor changes
changed page structure, added missing info
content added to the how to instrument page
content added in the main SMI overview
romansprykee
added
new
romansprykee
requested review from
vlunov-spryker,
gechetspr and
michalwroblewski-spryker
| ## Telemetry data in scope of Spryker Monitoring Integration | ||
| The Spryker Monitoring Integration focuses on several key entities to provide comprehensive monitoring: | ||
|
|
||
| ### Traces and Spans |
There was a problem hiding this comment.
it is already explained in How to Instrument shall we link to this section?
| The default metrics resolution is 60 seconds. All metrics can be split by telemetry-data-account. | ||
|
|
||
| ## How do I get it? | ||
| ### Prerequisites |
There was a problem hiding this comment.
shall we mention also commercials have to be signed before?
There was a problem hiding this comment.
@romansprykee yes, let's mentioned that as soon as the agreement for this SKU is concluded.
gechetspr
approved these changes
Feb 12, 2025
| The Spryker Monitoring Integration focuses on several key entities to provide comprehensive monitoring: | ||
|
|
||
| ### Traces and Spans | ||
| In OpenTelemetry, a **trace** represents the journey of a single request or transaction as it moves through various components of a system, capturing the end-to-end flow. A **span** is a single operation or unit of work within a trace, containing information like the operation name, start and end times, and any relevant metadata. Together, traces and spans provide a detailed view of the interactions and performance of different parts of an application, helping to diagnose issues and optimize performance. |
There was a problem hiding this comment.
@gechetspr let's add here the supported version of OTEL convention - 1.30. As a highlighted box.
vlunov-spryker
requested changes
Feb 13, 2025
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.
PR labels
When the PR is ready for review, add a TW review needed label. This lets us keep track of PRs that need to be merged and merge them in time.
PR Description
Describe the context for your changes and the changes you've made.
Tickets
If changes are associated with a ticket, add a docs ticket here.
Checklist