{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":708641532,"defaultBranch":"node-v20.x-nsolid-v5.x","name":"nsolid","ownerLogin":"nodesource","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2023-10-23T04:45:29.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/6759417?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1717432023.0","currentOid":""},"activityList":{"items":[{"before":"075e2e65d930a82d664b84ce7cb492fa0c17af02","after":"5f93f68f9283fb9dc901b6071c31f42a6bc6949b","ref":"refs/heads/santi/otlp_envs","pushedAt":"2024-06-07T11:41:55.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"santigimeno","name":"Santiago Gimeno","path":"/santigimeno","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1084056?s=80&v=4"},"commit":{"message":"agents: allow using OTLP env variable in OTLPAgent\n\nThe configuration of the OTLPAgent is IMHO a bit clunky. The are 2\nconfiguration params/env variables: `NSOLID_OTLP` and\n`NSOLID_OTLP_CONFIG`.\n`NSOLID_OTLP` can take multiple values depending on the backend we're\nplanning to send the data to: `datadog`, `dynatrace`, `newrelic` and\n`otlp`.\n`NSOLID_OTLP_CONFIG` takes a JSON object with the config which has\ndifferent format depending on the `NSOLID_OTLP` value.\nFor the case of `otlp` the format of the config is something like this:\n```\n{\n  url: 'http://endpoint:port',\n  protocol: 'http' // or 'grpc'\n}\n```\nThis only gets us so far: what happens if I want to add a key in a\nspecific heep header? what if I want to send metrics to and endpoint and\ntraces to a different one? I could keep adding fields to the config\nobject but, do we want this?\nLuckily the OTLP exporter spec defines a series of standard env\nvariables which allows for very granular configuration of the exporter\n(https://opentelemetry.io/docs/specs/otel/protocol/exporter/).\nThese env variables are supported by default by `opentelemetry-cpp`\nlibrary we're using.\nTo enable this, a very slight modification of `NSOLID_OTLP` and\n`NSOLID_OTLP_CONFIG` is needed. In the event we want the agent to use\nthese variables we'll need to configure only `NSOLID_OTLP=otlp` and not\nconfigure `NSOLID_OTLP_CONFIG`, which was required until now. In case we\nuse this new configuration and no OTLP_* env variable is used, the agent\nwill be launched configure with the default values defined in\nhttps://opentelemetry.io/docs/specs/otel/protocol/exporter/\n\nSo for example, now if we want to send metrics using grpc to endpoint1\nand traces using http to endpoint2 I would do it this way:\n```\nOTEL_EXPORTER_OTLP_METRICS_PROTOCOL=grpc\nOTEL_EXPORTER_OTLP_METRICS_ENDPOINT=http://endpoint1:${port}/v1/metrics\nOTEL_EXPORTER_OTLP_TRACES_PROTOCOL=http/protobuf # this could be omitted\nas it's the default\nOTEL_EXPORTER_OTLP_TRACES_ENDPOINT=http://endpoint2:${port}/v1/metrics\n./nsolid\n```","shortMessageHtmlLink":"agents: allow using OTLP env variable in OTLPAgent"}},{"before":"43d5f30b27220ffdfcff347f51b93247dca56861","after":"075e2e65d930a82d664b84ce7cb492fa0c17af02","ref":"refs/heads/santi/otlp_envs","pushedAt":"2024-06-03T16:34:55.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"santigimeno","name":"Santiago Gimeno","path":"/santigimeno","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1084056?s=80&v=4"},"commit":{"message":"agents: allow using OTLP env variable in OTLPAgent\n\nThe configuration of the OTLPAgent is IMHO a bit clunky. The are 2\nconfiguration params/env variables: `NSOLID_OTLP` and\n`NSOLID_OTLP_CONFIG`.\n`NSOLID_OTLP` can take multiple values depending on the backend we're\nplanning to send the data to: `datadog`, `dynatrace`, `newrelic` and\n`otlp`.\n`NSOLID_OTLP_CONFIG` takes a JSON object with the config which has\ndifferent format depending on the `NSOLID_OTLP` value.\nFor the case of `otlp` the format of the config is something like this:\n```\n{\n  url: 'http://endpoint:port',\n  protocol: 'http' // or 'grpc'\n}\n```\nThis only gets us so far: what happens if I want to add a key in a\nspecific heep header? what if I want to send metrics to and endpoint and\ntraces to a different one? I could keep adding fields to the config\nobject but, do we want this?\nLuckily the OTLP exporter spec defines a series of standard env\nvariables which allows for very granular configuration of the exporter\n(https://opentelemetry.io/docs/specs/otel/protocol/exporter/).\nThese env variables are supported by default by `opentelemetry-cpp`\nlibrary we're using.\nTo enable this, a very slight modification of `NSOLID_OTLP` and\n`NSOLID_OTLP_CONFIG` is needed. In the event we want the agent to use\nthese variables we'll need to configure only `NSOLID_OTLP=otlp` and not\nconfigure `NSOLID_OTLP_CONFIG`, which was required until now. In case we\nuse this new configuration and no OTLP_* env variable is used, the agent\nwill be launched configure with the default values defined in\nhttps://opentelemetry.io/docs/specs/otel/protocol/exporter/\n\nSo for example, now if we want to send metrics using grpc to endpoint1\nand traces using http to endpoint2 I would do it this way:\n```\nOTEL_EXPORTER_OTLP_METRICS_PROTOCOL=grpc\nOTEL_EXPORTER_OTLP_METRICS_ENDPOINT=http://endpoint1:${port}/v1/metrics\nOTEL_EXPORTER_OTLP_TRACES_PROTOCOL=http/protobuf # this could be omitted\nas it's the default\nOTEL_EXPORTER_OTLP_TRACES_ENDPOINT=http://endpoint2:${port}/v1/metrics\n./nsolid\n```","shortMessageHtmlLink":"agents: allow using OTLP env variable in OTLPAgent"}},{"before":null,"after":"f1571fce773e26047086728bcda49fd09a858c69","ref":"refs/heads/santi/enable_tracing_asap","pushedAt":"2024-06-03T16:27:03.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"santigimeno","name":"Santiago Gimeno","path":"/santigimeno","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1084056?s=80&v=4"},"commit":{"message":"agents: get telemetry data even if no cmd handle\n\nWe want the ZmqAgent to collect data (traces and/or metrics) even if the\nZMQ channels aren't fully up. This wasn't happening and we were losing\ndata because the tracing and metrics configuration options were not\nhandled until the ZmqCommandHandle wasn't ready.\n\nIdeally we should be able to collect traces even on initial loop\niteration without the need of calling `nsolid.start()`.  This should go\ninto a follow-up PR though.","shortMessageHtmlLink":"agents: get telemetry data even if no cmd handle"}},{"before":"babc9711f233d7435900e983dc7190a0f43c5bfa","after":null,"ref":"refs/heads/trevnorris/lint-fixes","pushedAt":"2024-05-31T20:59:12.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"trevnorris","name":"Trevor Norris","path":"/trevnorris","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/289174?s=80&v=4"}},{"before":"9c79696ac0a1463f73110c715f18a9e15db02a13","after":"babc9711f233d7435900e983dc7190a0f43c5bfa","ref":"refs/heads/node-v20.x-nsolid-v5.x","pushedAt":"2024-05-31T20:59:08.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"trevnorris","name":"Trevor Norris","path":"/trevnorris","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/289174?s=80&v=4"},"commit":{"message":"meta: lint fixes\n\nForgot to check the lint-js output from my last commit. Fix those\nerrors.\n\nPR-URL: https://github.com/nodesource/nsolid/pull/139\nReviewed-by: Santiago Gimeno <santiago.gimeno@gmail.com>","shortMessageHtmlLink":"meta: lint fixes"}},{"before":"8298ba101cf5d21cf864f6695ad3f69b0b6792f6","after":"babc9711f233d7435900e983dc7190a0f43c5bfa","ref":"refs/heads/trevnorris/lint-fixes","pushedAt":"2024-05-31T20:55:09.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"trevnorris","name":"Trevor Norris","path":"/trevnorris","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/289174?s=80&v=4"},"commit":{"message":"meta: lint fixes\n\nForgot to check the lint-js output from my last commit. Fix those\nerrors.\n\nPR-URL: https://github.com/nodesource/nsolid/pull/139\nReviewed-by: Santiago Gimeno <santiago.gimeno@gmail.com>","shortMessageHtmlLink":"meta: lint fixes"}},{"before":null,"after":"8298ba101cf5d21cf864f6695ad3f69b0b6792f6","ref":"refs/heads/trevnorris/lint-fixes","pushedAt":"2024-05-31T20:51:11.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"trevnorris","name":"Trevor Norris","path":"/trevnorris","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/289174?s=80&v=4"},"commit":{"message":"misc: lint fixes\n\nForgot to check the lint-js output from my last commit. Fix those\nerrors.","shortMessageHtmlLink":"misc: lint fixes"}},{"before":"87e3c184dadd8978ca980b3891a37636a5bca4ba","after":"43d5f30b27220ffdfcff347f51b93247dca56861","ref":"refs/heads/santi/otlp_envs","pushedAt":"2024-05-30T21:54:45.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"santigimeno","name":"Santiago Gimeno","path":"/santigimeno","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1084056?s=80&v=4"},"commit":{"message":"agents: allow using OTLP env variable in OTLPAgent\n\nThe configuration of the OTLPAgent is IMHO a bit clunky. The are 2\nconfiguration params/env variables: `NSOLID_OTLP` and\n`NSOLID_OTLP_CONFIG`.\n`NSOLID_OTLP` can take multiple values depending on the backend we're\nplanning to send the data to: `datadog`, `dynatrace`, `newrelic` and\n`otlp`.\n`NSOLID_OTLP_CONFIG` takes a JSON object with the config which has\ndifferent format depending on the `NSOLID_OTLP` value.\nFor the case of `otlp` the format of the config is something like this:\n```\n{\n  url: 'http://endpoint:port',\n  protocol: 'http' // or 'grpc'\n}\n```\nThis only gets us so far: what happens if I want to add a key in a\nspecific heep header? what if I want to send metrics to and endpoint and\ntraces to a different one? I could keep adding fields to the config\nobject but, do we want this?\nLuckily the OTLP exporter spec defines a series of standard env\nvariables which allows for very granular configuration of the exporter\n(https://opentelemetry.io/docs/specs/otel/protocol/exporter/).\nThese env variables are supported by default by `opentelemetry-cpp`\nlibrary we're using.\nTo enable this, a very slight modification of `NSOLID_OTLP` and\n`NSOLID_OTLP_CONFIG` is needed. In the event we want the agent to use\nthese variables we'll need to configure only `NSOLID_OTLP=otlp` and not\nconfigure `NSOLID_OTLP_CONFIG`, which was required until now. In case we\nuse this new configuration and no OTLP_* env variable is used, the agent\nwill be launched configure with the default values defined in\nhttps://opentelemetry.io/docs/specs/otel/protocol/exporter/\n\nSo for example, now if we want to send metrics using grpc to endpoint1\nand traces using http to endpoint2 I would do it this way:\n```\nOTEL_EXPORTER_OTLP_METRICS_PROTOCOL=grpc\nOTEL_EXPORTER_OTLP_METRICS_ENDPOINT=http://endpoint1:${port}/v1/metrics\nOTEL_EXPORTER_OTLP_TRACES_PROTOCOL=http/protobuf # this could be omitted\nas it's the default\nOTEL_EXPORTER_OTLP_TRACES_ENDPOINT=http://endpoint2:${port}/v1/metrics\n./nsolid\n```","shortMessageHtmlLink":"agents: allow using OTLP env variable in OTLPAgent"}},{"before":"b8c6f76d51f52ce6fbd409351d3e6b4ff246e7b1","after":"87e3c184dadd8978ca980b3891a37636a5bca4ba","ref":"refs/heads/santi/otlp_envs","pushedAt":"2024-05-30T21:54:05.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"santigimeno","name":"Santiago Gimeno","path":"/santigimeno","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1084056?s=80&v=4"},"commit":{"message":"agents: allow using OTLP env variable in OTLPAgent\n\nThe configuration of the OTLPAgent is IMHO a bit clunky. The are 2\nconfiguration params/env variables: `NSOLID_OTLP` and\n`NSOLID_OTLP_CONFIG`.\n`NSOLID_OTLP` can take multiple values depending on the backend we're\nplanning to send the data to: `datadog`, `dynatrace`, `newrelic` and\n`otlp`.\n`NSOLID_OTLP_CONFIG` takes a JSON object with the config which has\ndifferent format depending on the `NSOLID_OTLP` value.\nFor the case of `otlp` the format of the config is something like this:\n```\n{\n  url: 'http://endpoint:port',\n  protocol: 'http' // or 'grpc'\n}\n```\nThis only gets us so far: what happens if I want to add a key in a\nspecific heep header? what if I want to send metrics to and endpoint and\ntraces to a different one? I could keep adding fields to the config\nobject but, do we want this?\nLuckily the OTLP exporter spec defines a series of standard env\nvariables which allows for very granular configuration of the exporter\n(https://opentelemetry.io/docs/specs/otel/protocol/exporter/).\nThese env variables are supported by default by `opentelemetry-cpp`\nlibrary we're using.\nTo enable this, a very slight modification of `NSOLID_OTLP` and\n`NSOLID_OTLP_CONFIG` is needed. In the event we want the agent to use\nthese variables we'll need to configure only `NSOLID_OTLP=otlp` and not\nconfigure `NSOLID_OTLP_CONFIG`, which was required until now. In case we\nuse this new configuration and no OTLP_* env variable is used, the agent\nwill be launched configure with the default values defined in\nhttps://opentelemetry.io/docs/specs/otel/protocol/exporter/\n\nSo for example, now if we want to send metrics using grpc to endpoint1\nand traces using http to endpoint2 I would do it this way:\n```\nOTEL_EXPORTER_OTLP_METRICS_PROTOCOL=grpc\nOTEL_EXPORTER_OTLP_METRICS_ENDPOINT=http://endpoint1:${port}/v1/metrics\nOTEL_EXPORTER_OTLP_TRACES_PROTOCOL=http/protobuf # this could be omitted\nas it's the default\nOTEL_EXPORTER_OTLP_TRACES_ENDPOINT=http://endpoint2:${port}/v1/metrics\n./nsolid\n```","shortMessageHtmlLink":"agents: allow using OTLP env variable in OTLPAgent"}},{"before":"821c5a14eb7ed5b204f6ade3dbba3725334540a4","after":"b8c6f76d51f52ce6fbd409351d3e6b4ff246e7b1","ref":"refs/heads/santi/otlp_envs","pushedAt":"2024-05-30T21:50:13.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"santigimeno","name":"Santiago Gimeno","path":"/santigimeno","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1084056?s=80&v=4"},"commit":{"message":"agents: allow using OTLP env variable in OTLPAgent\n\nThe configuration of the OTLPAgent is IMHO a bit clunky. The are 2\nconfiguration params/env variables: `NSOLID_OTLP` and\n`NSOLID_OTLP_CONFIG`.\n`NSOLID_OTLP` can take multiple values depending on the backend we're\nplanning to send the data to: `datadog`, `dynatrace`, `newrelic` and\n`otlp`.\n`NSOLID_OTLP_CONFIG` takes a JSON object with the config which has\ndifferent format depending on the `NSOLID_OTLP` value.\nFor the case of `otlp` the format of the config is something like this:\n```\n{\n  url: 'http://endpoint:port',\n  protocol: 'http' // or 'grpc'\n}\n```\nThis only gets us so far: what happens if I want to add a key in a\nspecific heep header? what if I want to send metrics to and endpoint and\ntraces to a different one? I could keep adding fields to the config\nobject but, do we want this?\nLuckily the OTLP exporter spec defines a series of standard env\nvariables which allows for very granular configuration of the exporter\n(https://opentelemetry.io/docs/specs/otel/protocol/exporter/).\nThese env variables are supported by default by `opentelemetry-cpp`\nlibrary we're using.\nTo enable this, a very slight modification of `NSOLID_OTLP` and\n`NSOLID_OTLP_CONFIG` is needed. In the event we want the agent to use\nthese variables we'll need to configure only `NSOLID_OTLP=otlp` and not\nconfigure `NSOLID_OTLP_CONFIG`, which was required until now. In case we\nuse this new configuration and no OTLP_* env variable is used, the agent\nwill be launched configure with the default values defined in\nhttps://opentelemetry.io/docs/specs/otel/protocol/exporter/","shortMessageHtmlLink":"agents: allow using OTLP env variable in OTLPAgent"}},{"before":null,"after":"821c5a14eb7ed5b204f6ade3dbba3725334540a4","ref":"refs/heads/santi/otlp_envs","pushedAt":"2024-05-30T21:48:54.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"santigimeno","name":"Santiago Gimeno","path":"/santigimeno","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1084056?s=80&v=4"},"commit":{"message":"agents: allow using OTLP env variable in OTLPAgent\n\nThe configuration of the OTLPAgent is IMHO a bit clunky. The are 2\nconfiguration params/env variables: `NSOLID_OTLP` and\n`NSOLID_OTLP_CONFIG`.\n`NSOLID_OTLP` can take multiple values depending on the backend we're\nplanning to send the data to: `datadog`, `dynatrace`, `newrelic` and\n`otlp`.\n`NSOLID_OTLP_CONFIG` takes a JSON object with the config which has\ndifferent format depending on the `NSOLID_OTLP` value.\nFor the case of `otlp` the format of the config is something like this:\n```\n{\n  url: 'http://endpoint:port',\n  protocol: 'http' // or 'grpc'\n}\n```\nThis only gets so that far: what happens if I want to add a key in a\nspecific heep header? what if I want to send metrics to and endpoint and\ntraces to a different one? I could keep adding fields to the config\nobject but, do we want this?\nLuckily the OTLP exporter spec defines a series of standard env\nvariables which allows for very granular configuration of the exporter\n(https://opentelemetry.io/docs/specs/otel/protocol/exporter/).\nThese env variables are supported by default by `opentelemetry-cpp`\nlibrary we're using.\nTo enable this, a very slight modification of `NSOLID_OTLP` and\n`NSOLID_OTLP_CONFIG` is needed. In the event we want the agent to use\nthese variables we'll need to configure only `NSOLID_OTLP=otlp` and not\nconfigure `NSOLID_OTLP_CONFIG`, which was required until now. In case we\nuse this new configuration and no OTLP_* env variable is used, the agent\nwill be launched configure with the default values defined in\nhttps://opentelemetry.io/docs/specs/otel/protocol/exporter/","shortMessageHtmlLink":"agents: allow using OTLP env variable in OTLPAgent"}},{"before":"9c79696ac0a1463f73110c715f18a9e15db02a13","after":null,"ref":"refs/heads/trevnorris/log-api","pushedAt":"2024-05-30T20:52:12.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"trevnorris","name":"Trevor Norris","path":"/trevnorris","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/289174?s=80&v=4"}},{"before":"9b03aaad751b9ed7a095a3aa44b8ef1e51000797","after":"9c79696ac0a1463f73110c715f18a9e15db02a13","ref":"refs/heads/node-v20.x-nsolid-v5.x","pushedAt":"2024-05-30T20:52:05.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"trevnorris","name":"Trevor Norris","path":"/trevnorris","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/289174?s=80&v=4"},"commit":{"message":"src: add log native and JS APIs\n\nAdd a C++ API to collect logs written with the nsolid JS API.\n\nPR-UR: https://github.com/nodesource/nsolid/pull/135\nReviewed-by: Santiago Gimeno <santiago.gimeno@gmail.com>","shortMessageHtmlLink":"src: add log native and JS APIs"}},{"before":"2fc3e371848320ac8f0fe7b6ef4af39de9233a93","after":"9c79696ac0a1463f73110c715f18a9e15db02a13","ref":"refs/heads/trevnorris/log-api","pushedAt":"2024-05-30T17:25:12.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"trevnorris","name":"Trevor Norris","path":"/trevnorris","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/289174?s=80&v=4"},"commit":{"message":"src: add log native and JS APIs\n\nAdd a C++ API to collect logs written with the nsolid JS API.\n\nPR-UR: https://github.com/nodesource/nsolid/pull/135\nReviewed-by: Santiago Gimeno <santiago.gimeno@gmail.com>","shortMessageHtmlLink":"src: add log native and JS APIs"}},{"before":"9b03aaad751b9ed7a095a3aa44b8ef1e51000797","after":null,"ref":"refs/heads/trevnorris/transform-statsd","pushedAt":"2024-05-29T22:19:32.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"trevnorris","name":"Trevor Norris","path":"/trevnorris","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/289174?s=80&v=4"}},{"before":"c621e1ff22afcbddc2044822e28b5a272ce53fce","after":"9b03aaad751b9ed7a095a3aa44b8ef1e51000797","ref":"refs/heads/node-v20.x-nsolid-v5.x","pushedAt":"2024-05-29T22:19:22.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"trevnorris","name":"Trevor Norris","path":"/trevnorris","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/289174?s=80&v=4"},"commit":{"message":"agents: add metrics transform API to agent\n\nAllow users to register a callback that will transform the metrics into\na std::string that will be written to the endpoint.\n\nIn order to do this some of the internals needed to be rewritten so that\nconfig() could be called from any thread. The internal usage of config()\nhas been renamed since it will always be called from the StatsDAgent\nthread.\n\nPR-URL: https://github.com/nodesource/nsolid/pull/123\nReviewed-by: Santiago Gimeno <santiago.gimeno@gmail.com>","shortMessageHtmlLink":"agents: add metrics transform API to agent"}},{"before":"f08389e928759587f31904b7c364ef0a11bebe48","after":"9b03aaad751b9ed7a095a3aa44b8ef1e51000797","ref":"refs/heads/trevnorris/transform-statsd","pushedAt":"2024-05-29T20:24:04.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"trevnorris","name":"Trevor Norris","path":"/trevnorris","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/289174?s=80&v=4"},"commit":{"message":"agents: add metrics transform API to agent\n\nAllow users to register a callback that will transform the metrics into\na std::string that will be written to the endpoint.\n\nIn order to do this some of the internals needed to be rewritten so that\nconfig() could be called from any thread. The internal usage of config()\nhas been renamed since it will always be called from the StatsDAgent\nthread.\n\nPR-URL: https://github.com/nodesource/nsolid/pull/123\nReviewed-by: Santiago Gimeno <santiago.gimeno@gmail.com>","shortMessageHtmlLink":"agents: add metrics transform API to agent"}},{"before":"7df55550ef2bbfa4cef70dd3c0ccc8900f0f0ea5","after":"f08389e928759587f31904b7c364ef0a11bebe48","ref":"refs/heads/trevnorris/transform-statsd","pushedAt":"2024-05-29T16:16:19.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"trevnorris","name":"Trevor Norris","path":"/trevnorris","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/289174?s=80&v=4"},"commit":{"message":"agents: add metrics transform API to agent\n\nAllow users to register a callback that will transform the metrics into\na std::string that will be written to the endpoint.\n\nIn order to do this some of the internals needed to be rewritten so that\nconfig() could be called from any thread. The internal usage of config()\nhas been renamed since it will always be called from the StatsDAgent\nthread.","shortMessageHtmlLink":"agents: add metrics transform API to agent"}},{"before":"76d05a0583a1cfe75b847a0316eed2ad6ad3334e","after":"7df55550ef2bbfa4cef70dd3c0ccc8900f0f0ea5","ref":"refs/heads/trevnorris/transform-statsd","pushedAt":"2024-05-29T16:13:53.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"trevnorris","name":"Trevor Norris","path":"/trevnorris","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/289174?s=80&v=4"},"commit":{"message":"agents: add metrics transform API to agent\n\nAllow users to register a callback that will transform the metrics into\na std::string that will be written to the endpoint.\n\nIn order to do this some of the internals needed to be rewritten so that\nconfig() could be called from any thread. The internal usage of config()\nhas been renamed since it will always be called from the StatsDAgent\nthread.","shortMessageHtmlLink":"agents: add metrics transform API to agent"}},{"before":"c621e1ff22afcbddc2044822e28b5a272ce53fce","after":null,"ref":"refs/heads/v20.14.0-merge","pushedAt":"2024-05-29T16:13:37.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"trevnorris","name":"Trevor Norris","path":"/trevnorris","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/289174?s=80&v=4"}},{"before":"f3a4bf4d90364fe4662432c86c540d154701734b","after":"50feddc98913ad93eb2017a6b5ce5875a1b065af","ref":"refs/heads/node-v18.x-nsolid-v5.x","pushedAt":"2024-05-28T19:53:54.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"trevnorris","name":"Trevor Norris","path":"/trevnorris","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/289174?s=80&v=4"},"commit":{"message":"Working on v5.2.4 Hydrogen","shortMessageHtmlLink":"Working on v5.2.4 Hydrogen"}},{"before":"b9fd821fc9d79fbfcebb2b2a22d78982a9d2e0cf","after":"c621e1ff22afcbddc2044822e28b5a272ce53fce","ref":"refs/heads/node-v20.x-nsolid-v5.x","pushedAt":"2024-05-28T19:50:52.000Z","pushType":"push","commitsCount":47,"pusher":{"login":"trevnorris","name":"Trevor Norris","path":"/trevnorris","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/289174?s=80&v=4"},"commit":{"message":"Working on v5.2.4 Iron","shortMessageHtmlLink":"Working on v5.2.4 Iron"}},{"before":"dfe9b62bfcf1cfc0c5200d4ecbcfe88b6fbe656c","after":"c621e1ff22afcbddc2044822e28b5a272ce53fce","ref":"refs/heads/v20.14.0-merge","pushedAt":"2024-05-28T19:50:13.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"trevnorris","name":"Trevor Norris","path":"/trevnorris","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/289174?s=80&v=4"},"commit":{"message":"Working on v5.2.4 Iron","shortMessageHtmlLink":"Working on v5.2.4 Iron"}},{"before":"bda292a068b01770c7233b0e25b463d0675efdc4","after":"dfe9b62bfcf1cfc0c5200d4ecbcfe88b6fbe656c","ref":"refs/heads/v20.14.0-merge","pushedAt":"2024-05-28T19:48:05.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"trevnorris","name":"Trevor Norris","path":"/trevnorris","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/289174?s=80&v=4"},"commit":{"message":"2024-05-28, Version 20.14.0-nsolid-v5.2.3 'Iron'\n\nPR-URL: https://github.com/nodesource/nsolid/pull/137\nReviewed-by: Santiago Gimeno <santiago.gimeno@gmail.com>","shortMessageHtmlLink":"2024-05-28, Version 20.14.0-nsolid-v5.2.3 'Iron'"}},{"before":null,"after":"bda292a068b01770c7233b0e25b463d0675efdc4","ref":"refs/heads/v20.14.0-merge","pushedAt":"2024-05-28T17:47:07.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"trevnorris","name":"Trevor Norris","path":"/trevnorris","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/289174?s=80&v=4"},"commit":{"message":"Merge tag 'v20.14.0' into v20.14.0-merge\n\n2024-05-28 Node.js v20.14.0 'Iron' (LTS) Release\nGit-EVTag-v0-SHA512: 34ae431d7ef1270c9535019bd40bdb4d5ca09181a743bbfa6412750a32f86043f7e91dd53872c37973693a96bfc15d6c3de2c7e3086156b3c651008d5d337985","shortMessageHtmlLink":"Merge tag 'v20.14.0' into v20.14.0-merge"}},{"before":"2abf6c4d8f6059bc8ef7eebfc86ccaf502b17d60","after":"76d05a0583a1cfe75b847a0316eed2ad6ad3334e","ref":"refs/heads/trevnorris/transform-statsd","pushedAt":"2024-05-28T17:23:18.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"trevnorris","name":"Trevor Norris","path":"/trevnorris","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/289174?s=80&v=4"},"commit":{"message":"WIP for testing issue","shortMessageHtmlLink":"WIP for testing issue"}},{"before":"ccb9be3e5600241f71f11a8a29a21e0f43eda6dc","after":"2abf6c4d8f6059bc8ef7eebfc86ccaf502b17d60","ref":"refs/heads/trevnorris/transform-statsd","pushedAt":"2024-05-24T22:58:58.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"trevnorris","name":"Trevor Norris","path":"/trevnorris","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/289174?s=80&v=4"},"commit":{"message":"WIP","shortMessageHtmlLink":"WIP"}},{"before":"1d8bdb8e286155a3db42d6c56aa78dc5510eb1a3","after":"ccb9be3e5600241f71f11a8a29a21e0f43eda6dc","ref":"refs/heads/trevnorris/transform-statsd","pushedAt":"2024-05-24T16:22:37.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"trevnorris","name":"Trevor Norris","path":"/trevnorris","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/289174?s=80&v=4"},"commit":{"message":"WIP","shortMessageHtmlLink":"WIP"}},{"before":"351137581bdd4eb7b2c644e603b7899d3141b425","after":"1d8bdb8e286155a3db42d6c56aa78dc5510eb1a3","ref":"refs/heads/trevnorris/transform-statsd","pushedAt":"2024-05-23T23:54:08.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"trevnorris","name":"Trevor Norris","path":"/trevnorris","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/289174?s=80&v=4"},"commit":{"message":"WIP","shortMessageHtmlLink":"WIP"}},{"before":null,"after":"f279c02d35c9ab3662e893fb17e97d2dd51663fb","ref":"refs/heads/santi/grpc_agent","pushedAt":"2024-05-23T10:14:57.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"santigimeno","name":"Santiago Gimeno","path":"/santigimeno","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1084056?s=80&v=4"},"commit":{"message":"WIP","shortMessageHtmlLink":"WIP"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEXyjDQAA","startCursor":null,"endCursor":null}},"title":"Activity · nodesource/nsolid"}