Ansible
PS DSC
Downloads:
23,938
Downloads of v 0.98.0:
123
Last Update:
16 Apr 2024
Package Maintainer(s):
Software Author(s):
- SignalFx
Tags:
splunk-otel-collector- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Splunk OpenTelemetry Collector
- 1
- 2
- 3
0.98.0 | Updated: 16 Apr 2024
- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
23,938
Downloads of v 0.98.0:
123
Maintainer(s):
Software Author(s):
- SignalFx
Tags:
splunk-otel-collectorSplunk OpenTelemetry Collector 0.98.0
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
Deployment Method: Individual Install, Upgrade, & Uninstall
To install Splunk OpenTelemetry Collector, run the following command from the command line or from PowerShell:
>
To upgrade Splunk OpenTelemetry Collector, run the following command from the command line or from PowerShell:
>
To uninstall Splunk OpenTelemetry Collector, run the following command from the command line or from PowerShell:
>
Deployment Method:
NOTE
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download splunk-otel-collector --internalize --source=https://community.chocolatey.org/api/v2/ -
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'" - Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade splunk-otel-collector -y --source="'INTERNAL REPO URL'" [other options]See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade splunk-otel-collector -y --source="'INTERNAL REPO URL'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install splunk-otel-collector
win_chocolatey:
name: splunk-otel-collector
version: '0.98.0'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'splunk-otel-collector' do
action :install
source 'INTERNAL REPO URL'
version '0.98.0'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller splunk-otel-collector
{
Name = "splunk-otel-collector"
Version = "0.98.0"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'splunk-otel-collector':
ensure => '0.98.0',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
WARNING
There are versions of this package awaiting moderation . See the Version History section below.
Package Approved
This package was approved as a trusted package on 16 Apr 2024.
Description
The Splunk OpenTelemetry Collector is a distribution of the OpenTelemetry Collector. It provides a unified way to receive, process, and export metric, trace, and log data for Splunk Observability Cloud.
Package Parameters
The following package parameters are available:
/SPLUNK_ACCESS_TOKEN: The Splunk access token (org token) used to send data to Splunk Observability Cloud./SPLUNK_REALM: The Splunk realm to send the data to. Default value isus0./SPLUNK_INGEST_URL:: URL of the Splunk ingest endpoint (e.g.https://ingest.us1.signalfx.com). Default value ishttps://ingest.$SPLUNK_REALM.signalfx.com./SPLUNK_API_URL: URL of the Splunk API endpoint (e.g.https://api.us1.signalfx.com). Default value ishttps://api.$SPLUNK_REALM.signalfx.com./SPLUNK_HEC_TOKEN: The Splunk HEC authentication token. Default value is the same asSPLUNK_ACCESS_TOKEN./SPLUNK_HEC_URL: URL of the Splunk HEC endpoint (e.g.https://ingest.us1.signalfx.com/v1/log). Default value ishttps://ingest.$SPLUNK_REALM.signalfx.com/v1/log/SPLUNK_TRACE_URL: URL of the Splunk trace endpoint (e.g.https://ingest.us1.signalfx.com/v2/trace). Default value ishttps://ingest.$SPLUNK_REALM.signalfx.com/v2/trace/SPLUNK_BUNDLE_DIR: The path to the Smart Agent bundle directory for thesmartagentreceiver and extension. The default path is provided by the Collector package. If the specified path is changed from the default value, the path should be an existing directory on the system. Default value is\Program Files\Splunk\OpenTelemetry Collector\agent-bundle./SPLUNK_LISTEN_INTERFACE: The network interface the collector receivers will listen on. Default value is127.0.0.1for agent mode and0.0.0.0for gateway./MODE: This parameter is used for setting the Collector configuration file to\ProgramData\Splunk\OpenTelemetry Collector\agent_config.yamlor\ProgramData\Splunk\OpenTelemetry Collector\gateway_config.yaml. Possible values areagentandgateway. Default value isagent./WITH_FLUENTD: Whether to download, install, and configure Fluentd to collect and forward log events to the Collector. Possible values aretrueandfalse. If set totrue, the Fluentd MSI package will be downloaded fromhttps://packages.treasuredata.com. Default value isfalse.
To pass parameters, use --params "''" (e.g. choco install splunk-otel-collector --params="'/SPLUNK_ACCESS_TOKEN:MY_SPLUNK_ACCESS_TOKEN /SPLUNK_REALM:MY_SPLUNK_REALM'").
To have choco remember parameters on upgrade, be sure to set choco feature enable -n=useRememberedArgumentsForUpgrades before installation.
See Chocolatey Installation for additional details.
Files
tools\chocolateyinstall.ps1
tools\chocolateyuninstall.ps1
$ErrorActionPreference = 'Stop'; # stop on all errors
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$packageArgs = @{
packageName = $env:ChocolateyPackageName
softwareName = $env:ChocolateyPackageTitle
fileType = 'MSI'
silentArgs = "/qn /norestart"
validExitCodes = @(0)
}
[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']
if ($key.Count -eq 1) {
$key | % {
$packageArgs['file'] = "$($_.UninstallString)" #NOTE: You may need to split this if it contains spaces, see below
if ($packageArgs['fileType'] -eq 'MSI') {
$packageArgs['silentArgs'] = "$($_.PSChildName) $($packageArgs['silentArgs'])"
$packageArgs['file'] = ''
}
Uninstall-ChocolateyPackage @packageArgs
}
} elseif ($key.Count -eq 0) {
Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
Write-Warning "$($key.Count) matches found!"
Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
Write-Warning "Please alert package maintainer the following keys were matched:"
$key | % {Write-Warning "- $($_.DisplayName)"}
}
tools\common.ps1
$installation_path = "${env:PROGRAMFILES}\Splunk\OpenTelemetry Collector"
$program_data_path = "${env:PROGRAMDATA}\Splunk\OpenTelemetry Collector"
$config_path = "$program_data_path\"
$service_name = "splunk-otel-collector"
try {
Resolve-Path $env:SYSTEMDRIVE 2>&1>$null
$fluentd_base_dir = "${env:SYSTEMDRIVE}\opt\td-agent"
} catch {
$fluentd_base_dir = "\opt\td-agent"
}
$fluentd_config_dir = "$fluentd_base_dir\etc\td-agent"
$fluentd_config_path = "$fluentd_config_dir\td-agent.conf"
$fluentd_service_name = "fluentdwinsvc"
$fluentd_log_path = "$fluentd_base_dir\td-agent.log"
# whether the service is running
function service_running([string]$name) {
return ((Get-CimInstance -ClassName win32_service -Filter "Name = '$name'" | Select Name, State).State -Eq "Running")
}
# whether the service is installed
function service_installed([string]$name) {
return ((Get-CimInstance -ClassName win32_service -Filter "Name = '$name'" | Select Name, State).Name -Eq "$name")
}
function get_service_log_path([string]$name) {
$log_path = "the Windows Event Viewer"
if (($name -eq $fluentd_service_name) -and (Test-Path -Path "$fluentd_log_path")) {
$log_path = $fluentd_log_path
}
return $log_path
}
# wait for the service to start
function wait_for_service([string]$name, [int]$timeout=60) {
$startTime = Get-Date
while (!(service_running -name "$name")){
if ((New-TimeSpan -Start $startTime -End (Get-Date)).TotalSeconds -gt $timeout) {
$err = "Timed out waiting for the $name service to be running."
$log_path = get_service_log_path -name "$name"
Write-Warning "$err"
Write-Warning "Please check $log_path for more details."
throw "$err"
}
# give windows a second to synchronize service status
Start-Sleep -Seconds 1
}
}
# wait for the service to stop
function wait_for_service_stop([string]$name, [int]$timeout=60) {
$startTime = Get-Date
while ((service_running -name "$name")){
if ((New-TimeSpan -Start $startTime -End (Get-Date)).TotalSeconds -gt $timeout) {
$err = "Timed out waiting for the $name service to be stopped."
$log_path = get_service_log_path -name "$name"
Write-Warning "$err"
Write-Warning "Please check $log_path for more details."
throw "$err"
}
# give windows a second to synchronize service status
Start-Sleep -Seconds 1
}
}
# start the service if it's stopped
function start_service([string]$name, [string]$config_path=$config_path, [int]$max_attempts=3, [int]$timeout=60) {
if (!(service_installed -name "$name")) {
throw "The $name service does not exist!"
}
if (!(service_running -name "$name")) {
if (Test-Path -Path $config_path) {
for ($i=1; $i -le $max_attempts; $i++) {
try {
Start-Service -Name "$name"
break
} catch {
$err = $_.Exception.Message
if ($i -eq $max_attempts) {
$log_path = get_service_log_path -name "$name"
Write-Warning "An error occurred while trying to start the $name service:"
Write-Warning "$err"
Write-Warning "Please check $log_path for more details."
throw "$err"
} else {
Stop-Service -Name "$name" -ErrorAction Ignore
Start-Sleep -Seconds 10
continue
}
}
}
wait_for_service -name "$name" -timeout $timeout
} else {
throw "$config_path does not exist and is required to start the $name service"
}
}
}
# stop the service if it's running
function stop_service([string]$name, [int]$max_attempts=3, [int]$timeout=60) {
if ((service_running -name "$name")) {
for ($i=1; $i -le $max_attempts; $i++) {
try {
Stop-Service -Name "$name"
break
} catch {
$err = $_.Exception.Message
if ($i -eq $max_attempts) {
$log_path = get_service_log_path -name "$name"
Write-Warning "An error occurred while trying to start the $name service:"
Write-Warning "$err"
Write-Warning "Please check $log_path for more details."
throw "$err"
} else {
Start-Sleep -Seconds 10
continue
}
}
}
wait_for_service_stop -name "$name" -timeout $timeout
}
}
# remove registry entries created by the splunk-otel-collector service
function remove_otel_registry_entries() {
try {
if (Test-Path "HKLM:\SYSTEM\CurrentControlSet\Services\EventLog\Application\splunk-otel-collector"){
Remove-Item "HKLM:\SYSTEM\CurrentControlSet\Services\EventLog\Application\splunk-otel-collector"
}
} catch {
$err = $_.Exception.Message
$message = "
unable to remove registry entries at HKLM:\SYSTEM\CurrentControlSet\Services\EventLog\Application\splunk-otel-collector
$err
"
throw "$message"
}
}
function set_env_var_value_from_package_params([hashtable] $env_vars, [hashtable] $package_params, [string]$name, [string]$default_value) {
$value = $package_params[$name]
if ($value) {
# If the variable was passed as a package parameter, use that value.
$env_vars[$name] = $value
return
}
# If the variable was not passed as a package parameter, check if it was already set in the environment.
$value = $env_vars[$name]
if ($value) {
# If the variable already exists in the environment, use that value.
return
}
$value = "$default_value" # Env. var values are always strings.
$env_vars[$name] = $value
Write-Host "The $name package parameter was not set, using the default value: '$value'"
}
function set_service_environment([string]$service_name, [hashtable]$env_vars) {
Write-Host "Setting environment variables for the $service_name service..."
# Transform the $env_vars to an array of strings so the Set-ItemProperty correctly create the
# 'Environment' REG_MULTI_SZ value.
[string []] $multi_sz_value = ($env_vars.Keys | ForEach-Object { "$_=$($env_vars[$_])" } | Sort-Object)
$target_service_reg_key = Join-Path "HKLM:\SYSTEM\CurrentControlSet\Services" $service_name
if (Test-Path $target_service_reg_key) {
Set-ItemProperty $target_service_reg_key -Name "Environment" -Value $multi_sz_value
}
else {
throw "Invalid service '$service_name'. Registry key '$target_service_reg_key' doesn't exist."
}
}
# check that we're not running with a restricted execution policy
function check_policy() {
$executionPolicy = (Get-ExecutionPolicy)
$executionRestricted = ($executionPolicy -eq "Restricted")
if ($executionRestricted) {
throw @"
Your execution policy is $executionPolicy, this means you will not be able import or use any scripts including modules.
To fix this change you execution policy to something like RemoteSigned.
PS> Set-ExecutionPolicy RemoteSigned
For more information execute:
PS> Get-Help about_execution_policies
"@
}
}
# download a file to a given destination
function download_file([string]$url, [string]$outputDir, [string]$fileName) {
try {
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
(New-Object System.Net.WebClient).DownloadFile($url, "$outputDir\$fileName")
} catch {
$err = $_.Exception.Message
$message = "
An error occurred while downloading $url
$err
"
throw "$message"
}
}
# create the temp directory if it doesn't exist
function create_temp_dir($tempdir) {
if ((Test-Path -Path "$tempdir")) {
Remove-Item -Recurse -Force "$tempdir"
}
mkdir "$tempdir" -ErrorAction Ignore
}
function install_msi([string]$path) {
Write-Host "Installing $path ..."
$startTime = Get-Date
$proc = (Start-Process msiexec.exe -Wait -PassThru -ArgumentList "/qn /norestart /i `"$path`"")
if ($proc.ExitCode -ne 0 -and $proc.ExitCode -ne 3010) {
Write-Warning "The installer failed with error code ${proc.ExitCode}."
try {
$events = (Get-WinEvent -ProviderName "MsiInstaller" | Where-Object { $_.TimeCreated -ge $startTime })
ForEach ($event in $events) {
($event | Select -ExpandProperty Message | Out-String).TrimEnd() | Write-Host
}
} catch {
Write-Warning "Please check the Windows Event Viewer for more details."
continue
}
Exit $proc.ExitCode
}
Write-Host "- Done"
}
$ErrorActionPreference = 'Stop'; # stop on all errors
tools\fluentd.ps1
$fluentd_msi_name = "td-agent-4.3.2-x64.msi"
$fluentd_dl_url = "https://s3.amazonaws.com/packages.treasuredata.com/4/windows/$fluentd_msi_name"
try {
Resolve-Path $env:TEMP 2>&1>$null
$tempdir = "${env:TEMP}\Fluentd"
} catch {
$tempdir = "\tmp\Fluentd"
}
create_temp_dir -tempdir $tempdir
$default_fluentd_config = "$installation_path\fluentd\td-agent.conf"
$default_confd_dir = "$installation_path\fluentd\conf.d"
# copy the default fluentd config to $fluentd_config_path if it does not already exist
if (!(Test-Path -Path "$fluentd_config_path") -And (Test-Path -Path "$default_fluentd_config")) {
$default_fluentd_config = Resolve-Path "$default_fluentd_config"
Write-Host "Copying $default_fluentd_config to $fluentd_config_path"
mkdir "$fluentd_config_dir" -ErrorAction Ignore | Out-Null
Copy-Item "$default_fluentd_config" "$fluentd_config_path"
}
# copy the default source configs to $fluentd_config_dir\conf.d if it does not already exist
if (Test-Path -Path "$default_confd_dir\*.conf") {
mkdir "$fluentd_config_dir\conf.d" -ErrorAction Ignore | Out-Null
$confFiles = (Get-Item "$default_confd_dir\*.conf")
foreach ($confFile in $confFiles) {
$name = $confFile.Name
$path = $confFile.FullName
if (!(Test-Path -Path "$fluentd_config_dir\conf.d\$name")) {
Write-Host "Copying $path to $fluentd_config_dir\conf.d\$name"
Copy-Item "$path" "$fluentd_config_dir\conf.d\$name"
}
}
}
Write-Host "Downloading $fluentd_dl_url..."
download_file -url "$fluentd_dl_url" -outputDir "$tempdir" -fileName "$fluentd_msi_name"
$fluentd_msi_path = (Join-Path "$tempdir" "$fluentd_msi_name")
install_msi -path "$fluentd_msi_path"
# remove the temporary directory
Remove-Item -Recurse -Force "$tempdir"
tools\LICENSE.txt
From: https://raw.githubusercontent.com/signalfx/splunk-otel-collector/main/LICENSE
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
tools\splunk-otel-collector-0.98.0-amd64.msi
md5: 48A8B306947DCE5B80EB771F772B0456 | sha1: 8F79B42B91A2C99399B3E44F160424BAA2E4948E | sha256: 3ACC195C6D5F0EDEA3921152B51E7BA7C4DB2D89BDA7E2DCF4CF5C88DC09358B | sha512: 4D9CD306A7864F385515426BE4274D22AF13EF0B5935EA938B9CCFEEC73D651FF5A7F26EABCCB5DDFC5740DAEF59422CE69BC167D470F75A2E6BF669BF0EA65A
tools\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
This package is built and published by SignalFx, Inc.
Company: https://www.signalfx.com/
Repository: https://github.com/signalfx/splunk-otel-collector
License: https://github.com/signalfx/splunk-otel-collector/blob/main/LICENSE
splunk-otel-collector-0.98.0-amd64.msi checksum:
* SHA256: 3ACC195C6D5F0EDEA3921152B51E7BA7C4DB2D89BDA7E2DCF4CF5C88DC09358B
Virus Scan Results
Log in or click on link to see number of positives.
- splunk-otel-collector.0.98.0.nupkg (2359050749c5) - ## / 44
- splunk-otel-collector-0.98.0-amd64.msi (3acc195c6d5f) - ## / 49
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Version History
| Add to Builder | Version | Downloads | Last Updated | Status |
|---|---|---|---|---|
| Splunk OpenTelemetry Collector 0.99.0 | 2 | Friday, April 26, 2024 | Pending Automated Review | |
| Splunk OpenTelemetry Collector 0.98.0 | 123 | Tuesday, April 16, 2024 | Approved | |
| Splunk OpenTelemetry Collector 0.97.0 | 102 | Thursday, March 28, 2024 | Approved | |
| Splunk OpenTelemetry Collector 0.96.1 | 334 | Tuesday, March 12, 2024 | Approved | |
| Splunk OpenTelemetry Collector 0.96.0 | 12 | Monday, March 11, 2024 | Approved | |
| Splunk OpenTelemetry Collector 0.95.0 | 97 | Tuesday, March 5, 2024 | Approved | |
| Splunk OpenTelemetry Collector 0.94.0 | 66 | Friday, March 1, 2024 | Approved | |
| Splunk OpenTelemetry Collector 0.93.0 | 484 | Friday, February 9, 2024 | Approved | |
| Splunk OpenTelemetry Collector 0.92.0 | 369 | Friday, January 19, 2024 | Approved | |
| Splunk OpenTelemetry Collector 0.91.3 | 157 | Wednesday, January 10, 2024 | Approved | |
| Splunk OpenTelemetry Collector 0.91.2 | 30 | Tuesday, January 9, 2024 | Approved | |
| Splunk OpenTelemetry Collector 0.91.1 | 263 | Tuesday, December 19, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.91.0 | 69 | Tuesday, December 12, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.90.0 | 35 | Thursday, December 7, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.89.0 | 39 | Friday, December 1, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.88.0 | 98 | Thursday, November 16, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.86.0 | 374 | Tuesday, October 10, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.85.0 | 284 | Saturday, September 16, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.84.0 | 118 | Friday, September 8, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.83.0 | 274 | Friday, August 18, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.82.0 | 196 | Wednesday, August 2, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.81.1 | 73 | Friday, July 28, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.81.0 | 308 | Thursday, July 13, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.80.0 | 234 | Tuesday, June 27, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.79.1 | 75 | Friday, June 23, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.79.0 | 121 | Thursday, June 15, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.78.1 | 133 | Tuesday, June 6, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.78.0 | 61 | Wednesday, May 31, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.77.0 | 229 | Tuesday, May 16, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.76.1 | 106 | Saturday, May 6, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.76.0 | 59 | Tuesday, May 2, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.75.0 | 250 | Thursday, April 13, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.74.0 | 15717 | Tuesday, April 4, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.73.0 | 194 | Monday, March 20, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.72.0 | 192 | Thursday, March 9, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.71.0 | 42 | Tuesday, February 28, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.70.0 | 36 | Thursday, January 26, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.68.1 | 32 | Tuesday, January 10, 2023 | Approved | |
| Splunk OpenTelemetry Collector 0.67.0 | 179 | Friday, December 16, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.64.0 | 111 | Wednesday, November 16, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.63.0 | 60 | Friday, November 4, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.61.0 | 155 | Tuesday, October 4, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.60.0 | 48 | Friday, September 23, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.59.1 | 66 | Friday, September 9, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.58.0 | 49 | Tuesday, August 16, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.57.0 | 37 | Thursday, August 4, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.56.0 | 51 | Tuesday, July 26, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.55.1 | 54 | Wednesday, July 13, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.55.0 | 41 | Tuesday, July 12, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.54.0 | 86 | Tuesday, June 28, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.53.1 | 45 | Tuesday, June 21, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.53.0 | 55 | Wednesday, June 15, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.52.2 | 56 | Tuesday, June 7, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.52.1 | 42 | Wednesday, June 1, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.52.0 | 43 | Wednesday, June 1, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.51.0 | 47 | Thursday, May 19, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.50.1 | 50 | Thursday, May 5, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.50.0 | 41 | Monday, May 2, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.49.0 | 55 | Wednesday, April 27, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.48.0 | 63 | Thursday, April 7, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.47.1 | 44 | Wednesday, March 30, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.47.0 | 62 | Wednesday, March 23, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.46.0 | 52 | Wednesday, March 16, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.45.0 | 67 | Thursday, February 24, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.44.0 | 50 | Wednesday, February 16, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.43.0 | 57 | Thursday, January 27, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.42.0 | 52 | Monday, January 24, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.41.1 | 63 | Monday, January 10, 2022 | Approved | |
| Splunk OpenTelemetry Collector 0.41.0 | 51 | Monday, December 13, 2021 | Approved | |
| Splunk OpenTelemetry Collector 0.40.0 | 69 | Wednesday, December 1, 2021 | Approved | |
| Splunk OpenTelemetry Collector 0.39.0 | 60 | Saturday, November 20, 2021 | Approved | |
| Splunk OpenTelemetry Collector 0.37.0 | 91 | Thursday, November 11, 2021 | Approved |
Dependencies
-
- chocolatey-core.extension (≥ 1.3.5.1)
Discussion for the Splunk OpenTelemetry Collector Package
Ground Rules:
- This discussion is only about Splunk OpenTelemetry Collector and the Splunk OpenTelemetry Collector package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or Splunk OpenTelemetry Collector, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.