influxdata/telegraf

[inputs.openweathermap] Error in plugin: wrong/changed API endpoint for fetch type weather

Closed

#18,077 opened on Dec 2, 2025

View on GitHubContributor guide
 (4 comments) (0 reactions) (1 assignee)Go (5,831 forks)batch import
bughelp wantedsize/m

Repository metrics

Stars
 (17,731 stars)
PR merge metrics
 (Avg merge 2d 12h) (136 merged PRs in 30d)

Description

Relevant telegraf.conf

[[inputs.openweathermap]]
  ## OpenWeatherMap API key.
  app_id = "..."

  ## City ID's to collect weather data from.
  city_id = ["..."]

  # lang = "en"

  ## APIs to fetch; can contain "weather" or "forecast".
  fetch = ["weather"]

Logs from Telegraf

[inputs.openweathermap] Error in plugin: querying "https://api.openweathermap.org/data/2.5/group?APPID=...&id=...&lang=en&units=metric" failed: https://api.openweathermap.org/data/2.5/group?APPID=...&id=...&lang=en&units=metric returned HTTP status 401 Unauthorized

System info

Docker Container Telegraf 1.36.4

Docker

No response

Steps to reproduce

Try https://openweathermap.org/current They probably changed the API on August 29, 2025.

Expected behavior

Valid request

Actual behavior

File openweathermap.go line 220 should be weather instead of group

Additional info

No response

Contributor guide

Research direction
Locate the file plugins/inputs/openweathermap/openweathermap.go, find the API path for weather fetch (line 220), and change 'group' to 'weather'.
Tech stack
go
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85