2023-07-19 - Update to Feature Release
\nAs of this AppScope release, known issues include:
\n1580 Applications with the s bit set cannot be scoped. The system loader will emit a warning that the AppScope library cannot be preloaded; there will be no effect on the application beyond that.
2023-04-19 - Maintenance Release
\nAs of this AppScope release, known issues include:
\n1424 Scoping a Go application that was built without certain symbol names produces limited metrics, but no events. Work on a fix is in issue 1416.
\n1412 Node.js apps compiled as Position Independent Executables (PIE) seg fault when scoped.
\n2022-11-09 - Feature Release
\nAs of this AppScope release, known issues include:
\n#1258 If a network connection is closed, and then an attempt is made to send or receive data on the same connection, the scoped application can crash. This issue is present in all versions of AppScope prior to 1.2.2.
\n#1251 Changing configuration of a scoped, running process causes the process to crash when the new configuration defines a protocol that the old configuration also defines. It crashes as long as the two protocols have the same name, even if the two definitions are identical. This issue is present in all versions of AppScope prior to 1.2.2.
\n#1153 After AppScope detaches from a process, scope ps still shows the process as scoped.
#1055 With certain combinations of mount and PID namespaces, AppScope fails to attach to a process. We have found two scenarios when attach will fail. One is when AppScope is on a host and the target process is in a container, making the mount namespaces different, but the process was started with pid=host, making the PID namespaces the same. Another is when both AppScope and the target process are on a host, making the PID namespaces the same, but the process is configured as a service with PrivateTmp set to true, making the mount namespaces different.
2022-06-29 - Feature Release
\nAs of this AppScope release, known issues include:
\n#1017 Updated description: AppScope incorrectly handles the \"peek\" flag in interposed functions that receive network data. When a server \"peeks\" at the first byte of data, AppScope counts that byte twice, which breaks protocol detection. AppScope then fails to correctly produce HTTP events.
\n2022-04-12 - Maintenance Release
\nAs of this AppScope release, known issues include:
\n#869 AppScope's ability to avoid outputting binary data in console messages does not work perfectly in all situations. When data is first sent to the console by a scoped app, AppScope can detect whether it is binary, and if so, redact it while emitting an informative message. But when apps switch back and forth between textual and binary data, AppScope does not detect the change, and binary data can appear in console output.
\n2022-02-15 - GA
\nAs of this AppScope GA release, known issues include:
\nscope attach to GDB seems to break GDB.2021-12-21 - Maintenance Pre-Release
\nAs of this AppScope pre-release, known issues include:
\n#677 HTTP/1.1 events are parsed incorrectly, populating the http_method and http_target fields with junk.
2021-07-02 - Maintenance Pre-Release
\nAs of this AppScope pre-release, known issues include:
\n#362 AppScope cannot attach to any musl libc process.
\n2021-04-01 - Maintenance Pre-Release
\nAs of this AppScope pre-release, known issues include:
\n#640 On Alpine and other distributions based on musl libc, running appscope attach against a Go application fails with the error: failed to find libc in target process.
#35 Go executables with stripped symbols do not allow function interposition. Executables will run, but will not provide data to AppScope.
\n#143 Linux distros that use uClibc or MUSL instead of glibc, such as Alpine, are not supported
\n#10, #165, Scoping the Docker executable is problematic.
\n#119 HTTP 2 metrics and headers can be viewed only with Cribl LogStream.
\nSee all issues currently open on GitHub.
","frontmatter":{"title":"Known Issues"}}},"pageContext":{"slug":"/known-issues/","id":"17940ad4-44da-5247-aa50-0b409082d180"}},"staticQueryHashes":["2787008656","306729481","625673991","640077088"]}