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

DATAGO-85698: Jira tickets should be created from C-EMA error logs #212

Closed
wants to merge 2 commits into from

Conversation

CameronRushton
Copy link
Collaborator

What is the purpose of this change?

Add the CEMA ID to the logs so that it shows up in our monitoring

How was this change implemented?

Add the EMA ID to MDC

How was this change tested?

Deploying a copy of the EMA and testing the monitor in dev

Is there anything the reviewers should focus on/be aware of?

None

Copy link

SonarQube Quality Gate

Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@CameronRushton CameronRushton marked this pull request as ready for review November 25, 2024 20:03
@@ -26,7 +26,7 @@
<if condition='property("USE_JSON").equals("true")'>
<then>
<encoder class="net.logstash.logback.encoder.LogstashEncoder">
<customFields>{"component":"event-management-agent-${agentId}"}</customFields>
<customFields>{"component":"event-management-agent-${agentId}", "ema_id":"${agentId}"}</customFields>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since the agentId is already mentioned in the component value, can we use that value instead?

Merging this change would mean, releasing a new EMA after running tests, updating all production C-EMAs. So it would be great if we can use the existing value from component instead.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We absolutely can. That would have saved me a lot of time. I'll edit and re-test the monitor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants