You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to keep customers up-to-date with known issues with our new Opensearch-based logging system, we have documented the issues reported to us here.
If you encounter an issue not listed below, please describe it in an email to [email protected].
Update on the CSV reports missing Timestamp issue, there's a potentially easier workaround
Export the saved search
Edit the .ndjson file and add "timestamp" the config like below
a. Before: {"attributes":{"columns":["data.clusterName","data.realmId","data.type"....
b. After: {"attributes":{"columns":["timestamp","data.clusterName","data.realmId","data.type"
Import the .ndjson file back to saved objects. Now you can see the timestamp column and it's visible in the CSV report.
The content you are editing has changed. Please copy your edits and refresh the page.
In order to keep customers up-to-date with known issues with our new Opensearch-based logging system, we have documented the issues reported to us here.
If you encounter an issue not listed below, please describe it in an email to [email protected].
Update on the CSV reports missing Timestamp issue, there's a potentially easier workaround
a. Before:
{"attributes":{"columns":["data.clusterName","data.realmId","data.type"....
b. After:
{"attributes":{"columns":["timestamp","data.clusterName","data.realmId","data.type"
Known Issues
The text was updated successfully, but these errors were encountered: