Co-relating logs
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 28/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- java
- Domain
- observability-sre
Research direction
The issue names handler invocations, progress requests, and locally scheduled re-invocations but no files or tests. Start by tracing where these log entries are emitted and how invocation context is carried between calls. Done means the related entries can be reliably searched using a consistent request or correlation identifier.
Written by the indexing model from the issue text.
Description
Hi!
At the moment there's no way of co-relating log entries outputted from the handler.
An invocation (without customer log calls would look like:
2020-01-14T19:14:17.627+01:00 | Record Handler Progress with Request Id <RequestId> and Request: {RecordHandlerProgressRequest(BearerToken=<token> OperationStatus=IN_PROGRESS, CurrentOperationStatus=PENDING, ClientRequestToken=<token>)}
2020-01-14T19:14:18.283+01:00 | [CREATE] invoking handler...
2020-01-14T19:14:20.304+01:00 | [CREATE] handler invoked
2020-01-14T19:14:20.338+01:00 | Handler returned IN_PROGRESS
2020-01-14T19:14:20.474+01:00 | Record Handler Progress with Request Id <RequestId2> and Request: {RecordHandlerProgressRequest(BearerToken=<token>, OperationStatus=IN_PROGRESS, CurrentOperationStatus=IN_PROGRESS, ResourceModel={"attr": 123}, ClientRequestToken=<token>)}
2020-01-14T19:14:20.504+01:00 | Scheduling re-invoke locally after 1 seconds, with Context {RequestContext(invocation=1, callbackContext=CallbackContext(var1=123, var2=321), cloudWatchEventsRuleName=null, cloudWatchEventsTargetId=null)}
2020-01-14T19:14:21.541+01:00 | [CREATE] invoking handler...
2020-01-14T19:14:21.641+01:00 | [CREATE] handler invoked
2020-01-14T19:14:21.667+01:00 | Handler returned SUCCESS
The problem at the moment is that we do not have the possibility to co-relate those log entries easily through search.
Is it possible to maybe have the requestId as a prefix to all log entries? or some sort of correlational token like a transactionID?
Thanks!
- Dominant language
- Java
- Stars
- 30
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aws-cloudformation/cloudformation-cli-java-plugin
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
aws-cloudformation/cloudformation-cli-java-plugin#415 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
injectCredentialsAndInvokeV2 method in proxy class doesn't support API's like PutObject from S3. Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in aws-cloudformation/cloudformation-cli-java-plugin
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
[BUG]茶杯方块在取茶时会引发崩溃 Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
1.0.0-alpha2 Type/Improvement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
wso2/dpdp-accelerator#272 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
apache/rocketmq-dashboard#4860 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·