• network status
• geolocation?
• battery level?

Move these attributes over from #4

ensure the memory sampling instrumentation follows spec & sampling rate is configurable
https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/semantic_conventions/system-metrics.md

Allow authorization headers to be added via configuration to the GRPC connection used for Otel exporter.

how is service.name set, other attributes attached to resources. These data points are captured by the opentelementry-swift sdk, but we should provide links to these details.

Currently the agent support secret tokens but as far as I can see, does not support api key authentication unless using OTEL_EXPORTER_OTLP_HEADERS.

The generateMetadata function would need to be modified to supply a header of format "Authorization: ApiKey XXXX" if providing an api key.

The instrumentation provided in otel-swift and this agent project are enabled by default with no way to disable them.

Add configuration for instrumentation:

• NetworkStatus
• CPUSampler
• MemorySampler
• UIApplicationInstrumentation
• ViewControllerInstrumentation

This seems like a common issue with sources with different clocks. It'll need to be normalized in the backend.
APM-Server ticket here : elastic/apm-server#5173

This is a coordination between existing connectivity attributes implemented in RUM and the OpenTelemetry Spec.
Open-Telemetry spec : open-telemetry/opentelemetry-specification#1647

once finalized the attributes need to be promoted in apm server & added to ECS.

otel grpc channel needs to be configurable for secure or insecure setting. Now it needs to be manually changed in the code.

The network request failed due to a network error : "Network Connection was Lost"
so there shouldn't be an http response associated.

Kibana uses this value to categorize applications.

Open telemetry spec here

https://github.com/open-telemetry/opentelemetry-specification/blob/b46bcab5fb709381f1fd52096a19541370c7d1b3/specification/resource/semantic_conventions/deployment_environment.md

The GRPC client provides a means to enable logging. Provide a means to enable/disable this feature through the agent configuration.

Currently, the only metric exporter available in otel-swift is for prometheus.

• os version
• app version
• app name
• bundle id
• device model
• device identifier

Contents of product's NOTICE.txt file
For each dependency, contents of dependency's NOTICE.txt (if existing)
For each dependency, the full and exact license text copied from dependency's distribution/repository

SessionManager.swift has a hard coded timeout period set to 30 minutes. This should be configurable.

Product source code files all have appropriate license headers

todo:

• write appium script : elastic/opbeans-swift#3
• add saucelabs credentials to vault
• automated script that pulls edge + saucelabs creds from vault to automate saucelabs run.
• add build process that uploads opbeans-swift ipa file to saucelabs for testing

Each dependency reviewed and either in the Green List or has an exception (Note that the Yellow List contains a few automatic exceptions)

Product repositories contain required notices

reported as a metric.
allow configuration for sample rate.

https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/semantic_conventions/system-metrics.md

seems like service maps isn't generated with just traces.

Hook into application lifecycle notifications and record them.

There are two application lifecycle pathways: via the "NSApplicationDelegate", and SwiftUI App object.
It may only be necessary to hook into one of these lifecycles.

Should networking errors also show up here?

Ensure all fields reported by the agent are aligned with the mobile agent spec in terms of field names and semantics.

• start transaction on the tap action (and finish it on ViewDidAppear on the controller)
• use a timer to finish a transaction if no action happens afterwards
• research on ways to properly name transactions (resulting from button clicks)

View Controller traces are being categorized as unknown in kibana.

The following attributes are still being categorized under 'label'. They need to be elevated to first class attributes and added to the ECS.

• service.namespace
• net.peer.name
• net.peer.port

Relevant otel conventions: resource contentions & trace conventions

• create buildable project in apm-agent-ios
• create jenkins job for apm-agent-ios using JJB/JJBB in apm-ci
• follow up with infra if any changes needed for mac-stadium mac-minis.

Third-party code contained in product repositories (including vendored code and copy/pasted code) is appropriately marked and exports NOTICE.txt and license information like other dependencies

Meta issue on ensuring the OSS checklist is complete:

• #75
• #76
• #77
• #78
• #79
• #80
• #81
• #82
• #83

https://developer.apple.com/documentation/foundation/1508628-url_loading_system_error_codes

such as: Timeout, dns failure, etc

Ticket to track the explratory-view efforts for mobile.

This is a high-level overview of the three documentation phases we'll need to go through prior to GAing the IOS agent documentation. Ping me whenever you're ready for one of these phases and I'll kick things off.

Phase one

Provide a home for documentation to live as the repo grows. This isn't public and will be disconnected from the doc build for now.

• Use the (slightly outdated) Agent documentation template to add a template for PHP documentation. Recent example: elastic/apm-agent-php#48.

Phase two

We've got some content now. Let's add apm-agent-ios to Elastic's doc build (user facing).

• Open a PR in elastic/docs to add to the build elastic/docs#2129
• Open infra ticket to add the elasticsearch/ci docs check to this repo
• Add the elasticsearch/ci docs webhook to the repo
• Update elastic/apm-contrib elastic/apm-contrib#49
• Update elastic/apm elastic/apm#450
• Update elastic/apm-dev https://github.com/elastic/apm-dev/pull/626
• Remove any remaining documentation content from readme and link to published docs #37

Phase three

Time to hook the IOS Reference into the rest of the Stack documentation.

• Link from stack documentation to the IOS Reference. I'm not creating a list yet, as docs are likely to change a lot before we get to this step. When the time comes, inspiration can be taken from elastic/observability-docs#383. stack doc for iOS elastic/observability-docs#792

The current URLSession auto-instrumentation requires the manual use of DDURLSessionDelegate when creating a new URLSession. It's also not possible to instrument the shared URLSession object using this method.
It should be possible to intercept the creation of NSURLSessions and inject an instrumentation specific delegate object that also forwards delegate in the parameter list.

This can be added to an exporter when processing spans.

In order to help debugging and gathering usage statistics, agents should use one of the following values for the User-Agent HTTP header:

• Header value should start with agent github repository as prefix and version apm-agent-${language}/${agent.version}.
• If both service.name and service.version are set, append (${service.name} ${service.version})
• If only service.name is set, append (${service.name})

An executable gherkin specification is also provided in user_agent.feature.

Examples:

• apm-agent-java/v1.25.0
• apm-agent-ruby/4.4.0 (myservice)
• apm-agent-python/6.4.0 (myservice v42.7)

reference spec : https://github.com/elastic/apm/blob/main/specs/agents/transport.md

Use this issue as a list of todos under the umbrella of UI for a 7.14 release.

the currently plan is to create a new button linking to the exploratory view from the standard apm view.

I'd really like to see some pre-defined exploratory-view settings, but it sounds like that might not be an options. We may need to write some docs on how to build exploratory views for recommended charts.

The "time spent by span type" chart is not populating on either the "Overview" page nor the "Transaction" page.

elastic/apm-server#5032

Add specific elements to create documentation for below. TBD whether they should be stored in-repo or elsewhere.

• installation instructions (general)
• how to initialize in an objective-c project
• initialize in a swift project w/o swift ui
• initialize in a swift project with swift ui

currently, collectorHost is not robust enough to accept a hostname with a prefixed "protocol".

• try to access span from SwiftUI components to overwrite the span name
• ViewController extension