-
Notifications
You must be signed in to change notification settings - Fork 51
Open
Description
Hi, I used Logster back in 2017 and love it. Using it again and it's working in dev but not prod or staging. While trying to troubleshoot it, I noticed two things:
- In the server logs I see that Logster is looking at different IPs. Is that normal?
Started GET "/logs/messages.json?filter=0_1_2_3_4_5" for 172.71.159.45 at 2024-04-18 04:52:18 +0000
Started GET "/logs/messages.json?filter=0_1_2_3_4_5" for 172.71.159.46 at 2024-04-18 04:52:30 +0000
Started GET "/logs/messages.json?filter=0_1_2_3_4_5" for 172.71.159.45 at 2024-04-18 04:52:36 +0000
Started GET "/logs/messages.json?filter=0_1_2_3_4_5" for 172.71.154.236 at 2024-04-18 04:53:15 +0000
Started GET "/logs/messages.json?filter=0_1_2_3_4_5" for 172.71.154.194 at 2024-04-18 04:53:54 +0000
Started GET "/logs/messages.json?filter=0_1_2_3_4_5" for 172.69.135.149 at 2024-04-18 04:54:33 +0000
Started GET "/logs/messages.json?filter=0_1_2_3_4_5" for 162.158.166.226 at 2024-04-18 04:55:12 +0000
- In dev, redis has many "logster-env-*" keys but none in staging.
Rails version is 4.2.9 (same app from 2017). I have this in Logster initializer:
Logster.set_environments(%i[local development qa staging production])
Logster.store = Logster::RedisStore.new
What am I doing wrong?
Thanks in advance!
Originally posted by @nahankid in #34 (comment)
Metadata
Metadata
Assignees
Labels
No labels