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

Spire - DD integration issues #5434

Closed
Kathiresan1201 opened this issue Aug 27, 2024 · 3 comments
Closed

Spire - DD integration issues #5434

Kathiresan1201 opened this issue Aug 27, 2024 · 3 comments
Assignees
Labels
triage/in-progress Issue triage is in progress

Comments

@Kathiresan1201
Copy link

Hi Team, I have recently upgraded to 1.8.11 and configured spire server and agent telemetry with below configuration. I’m able to see the metrics of spire agents without any issues, however spire server labels are not showing since I’m ingesting couple of spire environment logs/metrics into the same DD instance? anyway to uniquely identify spire server metrics?

Screenshot 2024-08-27 at 10 00 42 AM image

#2 Couple of entries of SDS.V3 captured as service in the agent logs with errors(error:null, received error from Stream secrets server), UID 1000 no user found, I’m using same image from the tag.
Could you help with the issues please?

image

note: the spire agent is not configured with unix workload attestor.

@amartinezfayo amartinezfayo self-assigned this Aug 27, 2024
@amartinezfayo amartinezfayo added the triage/in-progress Issue triage is in progress label Aug 27, 2024
@amartinezfayo
Copy link
Member

Thank you @Kathiresan1201 for opening the issue.

note: the spire agent is not configured with unix workload attestor.

The logs are suggesting that the agent was loaded with the unix workload attestor. Maybe the configuration changed after it was loaded? Have you tried restarting the agent?
If you already restarted the agent and still see this error, could you share the plugins section of the agent configuration?
Thanks.

@amartinezfayo
Copy link
Member

Hi @Kathiresan1201 did you have a chance to look at my previous comment? Is this still an issue?

@amartinezfayo
Copy link
Member

I'll go ahead and close this issue. Please re-open if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/in-progress Issue triage is in progress
Projects
None yet
Development

No branches or pull requests

3 participants
@amartinezfayo @Kathiresan1201 and others