{"action":"created","issue":{"url":"https://api.github.com/repos/jorgebastida/awslogs/issues/96","repository_url":"https://api.github.com/repos/jorgebastida/awslogs","labels_url":"https://api.github.com/repos/jorgebastida/awslogs/issues/96/labels{/name}","comments_url":"https://api.github.com/repos/jorgebastida/awslogs/issues/96/comments","events_url":"https://api.github.com/repos/jorgebastida/awslogs/issues/96/events","html_url":"https://github.com/jorgebastida/awslogs/issues/96","id":182624468,"number":96,"title":"Not all streams shown","user":{"login":"GeorgeDewar","id":5344417,"avatar_url":"https://avatars1.githubusercontent.com/u/5344417?v=3","gravatar_id":"","url":"https://api.github.com/users/GeorgeDewar","html_url":"https://github.com/GeorgeDewar","followers_url":"https://api.github.com/users/GeorgeDewar/followers","following_url":"https://api.github.com/users/GeorgeDewar/following{/other_user}","gists_url":"https://api.github.com/users/GeorgeDewar/gists{/gist_id}","starred_url":"https://api.github.com/users/GeorgeDewar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/GeorgeDewar/subscriptions","organizations_url":"https://api.github.com/users/GeorgeDewar/orgs","repos_url":"https://api.github.com/users/GeorgeDewar/repos","events_url":"https://api.github.com/users/GeorgeDewar/events{/privacy}","received_events_url":"https://api.github.com/users/GeorgeDewar/received_events","type":"User","site_admin":false},"labels":[{"id":168768307,"url":"https://api.github.com/repos/jorgebastida/awslogs/labels/help%20wanted","name":"help wanted","color":"159818","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2016-10-12T20:22:08Z","updated_at":"2017-04-07T22:18:45Z","closed_at":null,"body":"Using the latest version of awslogs, I cannot see all streams in some log groups. For example, `aws logs describe-log-streams --log-group-name <my-group-name>` returns ten log streams, but `awslogs streams <my-group-name>` only returns two or three (and it's not consistent).\n\nSimilarly, there are some streams I can specify using `awslogs get <my-group-name> <my-stream-name>`, while other streams which do exist return `No streams match your pattern '<my-stream-name>'.`\n\nRegardless of this, calling `awslogs get <my-group-name>` without specifying a stream name always seems to work and return all streams.\n\nAny ideas?\n"},"comment":{"url":"https://api.github.com/repos/jorgebastida/awslogs/issues/comments/292665356","html_url":"https://github.com/jorgebastida/awslogs/issues/96#issuecomment-292665356","issue_url":"https://api.github.com/repos/jorgebastida/awslogs/issues/96","id":292665356,"user":{"login":"vlcinsky","id":635911,"avatar_url":"https://avatars0.githubusercontent.com/u/635911?v=3","gravatar_id":"","url":"https://api.github.com/users/vlcinsky","html_url":"https://github.com/vlcinsky","followers_url":"https://api.github.com/users/vlcinsky/followers","following_url":"https://api.github.com/users/vlcinsky/following{/other_user}","gists_url":"https://api.github.com/users/vlcinsky/gists{/gist_id}","starred_url":"https://api.github.com/users/vlcinsky/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vlcinsky/subscriptions","organizations_url":"https://api.github.com/users/vlcinsky/orgs","repos_url":"https://api.github.com/users/vlcinsky/repos","events_url":"https://api.github.com/users/vlcinsky/events{/privacy}","received_events_url":"https://api.github.com/users/vlcinsky/received_events","type":"User","site_admin":false},"created_at":"2017-04-07T22:18:45Z","updated_at":"2017-04-07T22:18:45Z","body":"I run into the same problem.\r\n\r\nTrying to list streams in my logs I got nothing.\r\n\r\nThere are few options for listing streams:\r\n- \"too few\": as today: without specifying time range very often no result\r\n- \"too many\": for streams, always retrieve all streams found in logs.\r\n- \"reasonable time range default\": agree e.g. on \"last one hour\" as default time range.\r\n\r\nThe \"too few\" is disappointing and surprising. To get good results, one has to find out about time ranges and use them.\r\n\r\n\"Too many\" can go sometime really wild (e.g. on long running AWS Lambda each worker creates new stream), but the result is not so big surprise. Natural reaction after this flood of streams is \"can I limit it by time range?\" and `awslogs` gives very good answer to that. In case, someone uses just few streams (as we do for collecting long term data from few sources), the \"too many\" is not an issue.\r\n\r\n\"reasonable time range default\" sounds good, but it could get tricky. The biggest problem is, that users will often feel \"something is not as I expected\", but will not find the solution easily as the problem will be partially hidden.\r\n\r\nSo I would prefer (for listing streams) the \"give me all which ever existed\" solution (what sometime translates into \"too many\")."}}
{"actor":{"display_login":"vlcinsky"}}