-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Report profiling data in v2.4 intake format; compress files (#53)
* Report profiling data in v2.4 intake format This was tested with both the Ruby (agent and agentless modes) and the PHP profilers. This also introduces a breaking API change: the `ddog_ProfileExporter_build` / `ProfileExporter::build` functions now take two additional arguments -- the profiling library name and version. Other than that change, using the v2.4 intake format is transparent to the libdatadog users. Thanks to @morrisonlevi for pairing with me on this. Note that this does not (yet) include support for including attributes in the reporting data. I'll leave that for a separate PR. * Adjust profiler_tags encoding * Remove data[] from the name of the files * Add lz4 compression to files * Don't compress event.json * Rename profile_library_[name|version] to profiling_library_[name|version] * Test for DD-EVP-ORIGIN* * Move profiling_library_{name,version} to constructor * Document some intake details Co-authored-by: Levi Morrison <levi.morrison@datadoghq.com>
- Loading branch information
1 parent
78969e5
commit 5b5a120
Showing
8 changed files
with
200 additions
and
34 deletions.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters