1 Answer
- Newest
- Most votes
- Most comments
3
In addition to the suggestions in the Stack Overflow post, here is some further info on how the Logs Insights URLs are generated that may help you.
The deep link of Logs Insights query is generated in three steps:
Step 1. Define the queryDetails in a JSON structure
{
editorString: '',
end: '',
queryId: '',
source: '',
start: '',
timeType: '',
tz: '',
unit: ''
};
Step 2. It uses jsurl (https://www.npmjs.com/package/jsurl) to encode the JSON object logs-insights?queryDetail=<encoded js url>
Step 3. It uses following map to replace the special characters inside logs-insights?queryDetail=<encoded js url>
{
'!' = '$21',
'#' = '$23',
'%' = '$25',
'&' = '$26',
// Spaces are encoded as +. That's what GWT uses when we do not manually
// encode our routes, so it is backwards compatible with customer links
// generated prior to this manual encoding process.
' ' = '$2B',
':' = '$3A',
';' = '$3B',
'=' = '$3D',
'?' = '$3F',
}
Step 4. add prefix https://console.aws.amazon.com/cloudwatch/home?region=<region>#logsV2:
To get more details, you can use some example URL and reverse the steps and see what the original JSON structure looks like.
Relevant content
- asked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 7 months ago