Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Datasource: JSON #21

Closed
Rello opened this issue Feb 4, 2020 · 3 comments
Closed

Datasource: JSON #21

Rello opened this issue Feb 4, 2020 · 3 comments
Assignees
Milestone

Comments

@Rello
Copy link
Owner

Rello commented Feb 4, 2020

Provide a datasource to read json data by a given array-string

Input Parameter:

  • URL of json
  • Authentification
  • json path
  • timestamp t/f

Use Case / Example:
Monitor the Nextcloud instance via its internal API

Example Output:
Screenshot 2020-02-04 at 21 30 39

@Rello Rello added testing development finished; in testing datasource labels Feb 4, 2020
@Rello Rello added this to the 2.1.0 milestone Feb 4, 2020
@Rello Rello self-assigned this Feb 4, 2020
@Rello Rello mentioned this issue Feb 4, 2020
31 tasks
Rello added a commit that referenced this issue Feb 4, 2020
@Rello
Copy link
Owner Author

Rello commented Feb 4, 2020

Rello added a commit that referenced this issue Feb 4, 2020
Rello added a commit that referenced this issue Feb 4, 2020
Rello added a commit that referenced this issue Feb 6, 2020
Rello added a commit that referenced this issue Mar 9, 2020
@Rello Rello added pending release part of the next release version and removed testing development finished; in testing pending release part of the next release version labels Mar 10, 2020
@Rello Rello closed this as completed Mar 11, 2020
@GH2204
Copy link

GH2204 commented Jul 5, 2022

Nice function!! I tried your Example 2 and it works fine.
Then i tried my own JSON - data-collector with API-Methode 2 at https://creativecommons.tankerkoenig.de/ (there is a demo-link within a demo-key) and it does not work. Where is the different?
I'd cut the JSON-request to one requested id: https://creativecommons.tankerkoenig.de/json/prices.php?ids=4429a7d9-fb2d-4c29-8cfe-2ca90323f9f8&apikey=[API-DEMO-KEY seen at https://creativecommons.tankerkoenig.de/] and in a browser it works.
used object-path: prices/4429a7d9-fb2d-4c29-8cfe-2ca90323f9f8/e5

Is there a problem with these URL-parameters ("ids", "apikey") or parsing the JSON-string?

@Rello
Copy link
Owner Author

Rello commented Jul 6, 2022

Hello,
there is an issue with de-/coding an & sign during the dataload. I will take care...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants