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

Refresh tracer metadata on CRaC snapshot restore #3036

Open
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

ArtyomGabeev
Copy link

@ArtyomGabeev ArtyomGabeev commented Feb 26, 2023

What does this PR do?

Checklist

Initial proposal for #2982

  • This is an enhancement of existing features, or a new feature in existing plugins
    • I have updated CHANGELOG.asciidoc
    • I have added tests that prove my fix is effective or that my feature works
    • Added an API method or config option? Document in which version this will be introduced
    • I have made corresponding changes to the documentation
  • This is a bugfix
  • This is a new plugin
    • I have updated CHANGELOG.asciidoc
    • My code follows the style guidelines of this project
    • I have made corresponding changes to the documentation
    • I have added tests that prove my fix is effective or that my feature works
    • New and existing unit tests pass locally with my changes
    • I have updated supported-technologies.asciidoc
    • Added an API method or config option? Document in which version this will be introduced
    • Added an instrumentation plugin? Describe how you made sure that old, non-supported versions are not instrumented by accident.
  • This is something else

@cla-checker-service
Copy link

cla-checker-service bot commented Feb 26, 2023

💚 CLA has been signed

@github-actions github-actions bot added agent-java community Issues and PRs created by the community triage labels Feb 26, 2023
@github-actions
Copy link

👋 @ArtyomGabeev Thanks a lot for your contribution!

It may take some time before we review a PR, so even if you don’t see activity for some time, it does not mean that we have forgotten about it.

Every once in a while we go through a process of prioritization, after which we are focussing on the tasks that were planned for the upcoming milestone. The prioritization status is typically reflected through the PR labels. It could be pending triage, a candidate for a future milestone, or have a target milestone set to it.

@apmmachine
Copy link
Collaborator

apmmachine commented Feb 26, 2023

❕ Build Aborted

The PR is not allowed to run in the CI yet

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Start Time: 2023-07-03T11:39:23.264+0000

  • Duration: 4 min 56 sec

Steps errors 2

Expand to view the steps failures

Load a resource file from a library
  • Took 0 min 0 sec . View more details here
  • Description: approval-list/elastic/apm-agent-java.yml
Error signal
  • Took 0 min 0 sec . View more details here
  • Description: githubApiCall: The REST API call https://api.github.com/orgs/elastic/members/ArtyomGabeev return the message : java.lang.Exception: httpRequest: Failure connecting to the service https://api.github.com/orgs/elastic/members/ArtyomGabeev : httpRequest: Failure connecting to the service https://api.github.com/orgs/elastic/members/ArtyomGabeev : Code: 404Error: {"message":"User does not exist or is not a member of the organization","documentation_url":"https://docs.github.com/rest/reference/orgs#check-organization-membership-for-a-user"}

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • run benchmark tests : Run the benchmark tests.

  • run jdk compatibility tests : Run the JDK Compatibility tests.

  • run integration tests : Run the Agent Integration tests.

  • run end-to-end tests : Run the APM-ITs.

  • run windows tests : Build & tests on windows.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@ArtyomGabeev ArtyomGabeev marked this pull request as ready for review February 26, 2023 16:25
@@ -143,6 +143,8 @@ private void completeMetaData(Context lambdaContext) {
String region = arnSegments[3];
String accountId = arnSegments[4];

String logStreamName = lambdaContext.getLogStreamName();
Copy link
Author

Choose a reason for hiding this comment

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

unfortunately, after snapshot restore, this method returns null, so lambda instance has <uknown> node name instead of CloudWatch log stream name.

AWS team replied, that this environment variable won't be available, since it's impossible to change env variables after snapshot it taken.

We need to decide for a fallback strategy, how to generate lambda instance identifier.

Copy link
Author

Choose a reason for hiding this comment

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

I've got a reply from AWS that neither AWS_LAMBDA_LOG_STREAM_NAME, neither context.getLogStreamName gonna be populated for SnapStart enabled functions - aws/aws-lambda-java-libs#402 .

I do not know, if Kibana product have some special handling of AWS lambda APM data and if it relies on the format of configured_name from service.node field.

In initial proposal, I suggest to simulate and generate similar to log group node name, but right now I think we do not need to tie (if possible) instance name to log group name at all.

If we need just to distinguish different lambda instances, may be pair of lambda version + ephemeral id is enough, but this is a breaking change, if we are going to change it for all AWS Lambdas.

Another option I'm considering is to introduce a property, which will be a strategy for lambda instance naming.
By default, we should still try to use AWS_LAMBDA_LOG_STREAM_NAME env variable, but we may allow another one, which will use auto generated name.

@botelastic
Copy link

botelastic bot commented May 8, 2023

Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as stalled to make it hit our filters and make sure we get back to it in as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

@botelastic botelastic bot added the stalled label May 8, 2023
@ArtyomGabeev
Copy link
Author

+1

@botelastic botelastic bot removed the stalled label May 8, 2023
@jackshirazi
Copy link
Contributor

jackshirazi commented Jun 15, 2023

Hi @ArtyomGabeev , thank you for this contribution it's really interesting! I'll be looking at this, it may take a little while as I'm also on other things. First thing though, can you please sign the contributor agreement

@ArtyomGabeev
Copy link
Author

I'm trying to sing contribution agreement, but do no receive any confirmation email.

@jackshirazi
Copy link
Contributor

You seem to have 2 email addresses, one is signed up but the one associated with this PR isn't. I've tried to add the latter email address, did you get an email?

@ArtyomGabeev
Copy link
Author

You seem to have 2 email addresses, one is signed up but the one associated with this PR isn't. I've tried to add the latter email address, did you get an email?

Thank you, looks like CLA is signed off.

@botelastic
Copy link

botelastic bot commented Sep 5, 2023

Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as stalled to make it hit our filters and make sure we get back to it in as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

@botelastic botelastic bot added the stalled label Sep 5, 2023
@ArtyomGabeev
Copy link
Author

+1

@botelastic botelastic bot removed the stalled label Sep 12, 2023
@botelastic
Copy link

botelastic bot commented Nov 11, 2023

Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as stalled to make it hit our filters and make sure we get back to it in as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

@botelastic botelastic bot added the stalled label Nov 11, 2023
@NicklasWallgren
Copy link
Contributor

+1

@botelastic botelastic bot removed the stalled label Nov 11, 2023
@botelastic
Copy link

botelastic bot commented Jan 10, 2024

Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as stalled to make it hit our filters and make sure we get back to it in as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

@botelastic botelastic bot added the stalled label Jan 10, 2024
@jackshirazi
Copy link
Contributor

still pending :+1

@botelastic botelastic bot removed the stalled label Jan 10, 2024
@v1v
Copy link
Member

v1v commented Feb 9, 2024

run docs-build

@botelastic
Copy link

botelastic bot commented Apr 9, 2024

Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as stalled to make it hit our filters and make sure we get back to it in as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

@botelastic botelastic bot added the stalled label Apr 9, 2024
@botelastic
Copy link

botelastic bot commented Apr 23, 2024

Hi! This issue has been stale for a while and we're going to close it as part of our cleanup procedure. We appreciate your contribution and would like to apologize if we have not been able to review it, due to the current heavy load of the team. Feel free to re-open this issue if you think it should stay open. Thank you for your contribution!

@botelastic botelastic bot closed this Apr 23, 2024
@jackshirazi jackshirazi reopened this May 2, 2024
@botelastic botelastic bot removed the stalled label May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
8.9-candidate agent-java community Issues and PRs created by the community triage
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants