KB article with opensearch documentation #2572
Merged
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
markdboyd
reviewed
Dec 3, 2024
pburkholder
force-pushed
the
peterb/migrating-to-opensearch
branch
from
3b196e3 to
616b582
Compare
pburkholder
changed the title
|
Issue:
|
markdboyd
reviewed
Dec 6, 2024
| The screenshot below show some of the major changes to the user interfaces, such as: | ||
| 1. The drop down menus have moved from the upper left to the upper right | ||
| 2. The "Top 5 values" for a field view is now an option to the right of the field, instead of a double-click | ||
| 3. There are a lot more values gathered for container metrics |
There was a problem hiding this comment.
This is true, but it's not a user interface change
markdboyd
reviewed
Dec 6, 2024
| * If you share the same saved object across multiple orgs, you will need to import it into each of your orgs. | ||
| * Better handling of large log messages. Both Kibana/ELK and OpenSearch have a 32kb limit on message size. The older system dropped such messages from Kibana (although they were still retained in cold storage), the newer system keeps the first 32kb and discards the rest | ||
| * Truncated messages are tagged with `_messagetrimmed`. | ||
| * Extremely large log messages (over 1Gb) are trimmed and tagged `_logtrimmed` -- such message are probably indicative of a coding error in your application. |
There was a problem hiding this comment.
There was a problem hiding this comment.
I thought 1Gb sounded high, so I must have mis-heard Jason. Fixing...
markdboyd
reviewed
Dec 6, 2024
| * Definitions of saved searches and visualizations are now isolated by OpenSearch tenants that correspond to Cloud.gov organizations. | ||
| * You no longer need to worry about choosing a globally unique name. | ||
| * If you share the same saved object across multiple orgs, you will need to import it into each of your orgs. | ||
| * Better handling of large log messages. Both Kibana/ELK and OpenSearch have a 32kb limit on message size. The older system dropped such messages from Kibana (although they were still retained in cold storage), the newer system keeps the first 32kb and discards the rest |
There was a problem hiding this comment.
Currently we're only truncating JSON messages that are over 32KB, but we probably should do it for all messages
markdboyd
reviewed
Dec 6, 2024
Perfect, thanks Co-authored-by: Mark Boyd <[email protected]> Signed-off-by: Peter Burkholder <[email protected]>
markdboyd
reviewed
Dec 6, 2024
|
|
||
| --- | ||
|
|
||
| ## What's Changing in December 2024 |
There was a problem hiding this comment.
Since the title of the post ("Migrating to the OpenSearch Dashboard for Cloud.gov log") renders as second-level heading, for semantics it could make sense to render these as third level headings and so on, but not a blocking suggestion
markdboyd
approved these changes
Dec 6, 2024
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.
Changes proposed in this pull request:
Security Considerations
Safe. Documents how to use a customer-facing service, without going into sensitive implementation details.