You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
#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?
note: the spire agent is not configured with unix workload attestor.
The text was updated successfully, but these errors were encountered:
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.
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?
#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?
note: the spire agent is not configured with unix workload attestor.
The text was updated successfully, but these errors were encountered: