Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ship worker logs to datadog #1502

Open
1 task
hackartisan opened this issue Feb 7, 2025 · 0 comments
Open
1 task

Ship worker logs to datadog #1502

hackartisan opened this issue Feb 7, 2025 · 0 comments
Labels
dls-work-cycle Tickets designated for the next work cycle (limit 16) sudden-priority

Comments

@hackartisan
Copy link
Member

hackartisan commented Feb 7, 2025

The worker machine doesn't appear to ship logs to datadog, and it also appears to truncate when the clock rolls over to a new day. We should have more log retention either on the box or in datadog.

sudden priority justification

We don't currently have visibility into the timing of our jobs. Lyrasis is observing api hits that concern them, and asking us about it.

Acceptance Criteria

  • There are logs for the production worker box in Datadog.

First Step

Go see how we're getting logs for the web boxes for pulfalight in princeton_ansible, and get it working that way for the worker box.

@hackartisan hackartisan added sudden-priority dls-work-cycle Tickets designated for the next work cycle (limit 16) labels Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dls-work-cycle Tickets designated for the next work cycle (limit 16) sudden-priority
Projects
None yet
Development

No branches or pull requests

1 participant