I have problem with writing data to influxDB cloud using Postman. I could't find my data in my bucket. How to write data on influxDB cloud with api?postman
From the postman screenshot, it looks like the request was successful. 204 no content is the success code; see https://docs.influxdata.com/influxdb/v2.1/api/#operation/PostWrite
The timestamp 1556813561098000000 in the lineprotocol you have is for Thu May 02 2019 16:12:41 GMT+0000 which is ~3 years ago. If you are using a free account on cloud2, the buckets will only keep data for the last 30 days. Try a more recent timestamp or leave the timestamp out to get a timestamp of "now".
Related
I'm attempting to use the Microsoft Graph API to query the sign in history of an app (https://learn.microsoft.com/en-us/graph/api/signin-list?view=graph-rest-1.0&tabs=http). It only returns at most the last 30 days worth of history. Is this by design or am I missing a parameter?
My filter string is
"(appId eq '_REDACTED_GUID_') and (createdDateTime ge 2020-11-01)"
I do not receive results prior to 30 days ago.
Azure AD stores sign-in data for the last 30 days. It is documented here depending on the plans.
We're working on migrating to Office365/M365 and when we make an API call to the Microsoft Management API for status, the statusTime field is yesterday. Any ideas why?
https://manage.office.com/api/v1.0/(tenant)/ServiceComms/CurrentStatus
Here's a partial json from the Exchange Online status:
"Status": "ServiceRestored",
"StatusDisplayName": "Service restored",
"StatusTime": "2018-10-01T18:49:36.4528522Z",
"Workload": "Exchange",
"WorkloadDisplayName": "Exchange Online"
StatusTime is exactly 1 day behind from my current timezone. The time appears to be in UTC but its UTC - 1 day. I'm confused why? I thought it would be current status.
Any ideas?
Thank you.
When you call to the Microsoft Management API for status, you will get a real-time view of current and ongoing service incidents and maintenance events.
If you want to display the current time zone, you could try to switch time zones locally.
The Microsoft Management API will not return your current timezone.
For more information, please review the following link: Get Current Status
We're using ejabberd as our xmpp server and iphone xmppframework for client side.
The problem is when we get the offline messages the timestap that is written in the message is in actual date/time format but the timezone of the server is different than the clients time zones so at this point the things are getting messy.
We're using a same approach while querying Last Activity of a user(XEP-0012) , but in last activity xep the server returns the information as "how many seconds ago the user last logged in to server" so in this way we can apply seconds difference to our clients time and found the message delivery date/time so there is no problem in Last Activity query.
But in delayed delivery , ejabberd sends an exact date and time value and clients confuses about the conversion(Date and time of each client may be very different from each others)
Does anyone know how can we fix that problem? Is there any way to configure ejabberd to return "seconds passed information" until offline message send ?
By the way we're using latest ejabberd version.
Thanks
XEP-0091 (Legacy Delayed Delivery) says:
The timezone is be understood as UTC.
So you need to convert the time from UTC to the local time of the client in order to get the correct result.
The newer specification, XEP-0203 (Delayed Delivery) also says:
[...] MUST be expressed in UTC
I have been using this msn weather api for couple of years now
Programatically access weather info
As of today I get the following error in my app. Access Denied. It could be a glitch or a permanent shutdown by microsoft. I don't know but is there any other free 4 day weather forecast api that I can use to get weather in a XML format? Saddest part is that I have been using this api in at least 20 of my apps and now I am scrambling to find a solution.
I did send an email to weather#microsoft.com couple of hours ago but as predicted no response.
2014-12-10 07:46:40.321 Big Clock[10890:230027] locationStr: http://weather.service.msn.com/data.aspx?weadegreetype=F&culture=en-US&weasearchstr=Detroit,MI
2014-12-10 07:46:40.461 Big Clock[10890:230027] XML:
<?xml version="1.0" encoding="utf-8"?><weatherdata xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><weather errormessage="Access denied: Please contact weather#microsoft.com if you need access to this API." /></weatherdata>
You are not alone in this.
For the time being, passing an additional query string "&src=outlook" worked for me.
Sample Working URL:
http://weather.service.msn.com/data.aspx?weasearchstr=45236&culture=en-US&weadegreetype=F&src=outlook
Try it out and see if it solves your issue.
This is Ram from Microsoft. The existing service will be deprecated soon.
Please resend your email to the alias one more time so we can take it offline. We had an email hiccup so the alias should work now.
Please do not use the outlook as src value.
We are writing to notify you that the Microsoft Weather API will no longer be available for download and will be discontinued as of April 15, 2015, meaning it will no longer provide weather data. Accordingly, please remove the Microsoft Weather API from any of your products or apps that currently use it.
Here is a list of external providers who might be able to support your needs if you are interested in obtaining an alternate weather API:
http://api.accuweather.com/
http://www.wunderground.com/weather/api/d/pricing.html?MR=1
https://developer.forecast.io/
Disclaimer: Microsoft and Microsoft Weather are not affiliated or associated with any of the above companies in any way.
Thank You
Microsoft Weather Team
Thanks to Ram we now know that MSN weather api will be gone by April 15th, 2015.
If anyone wants a free weather alternate then try this
http://openweathermap.org/price_detailes
Calls per minute (no more than) 3,000
Calls per day (no more than) 4,000,000
This is the most I have seen any weather provide give out for free. I hope it helps.
I keep getting 401 when trying to login via Oauth with Twitter.
I'm using twitter_oauth-0.3.3 with oauth-0.3.6 in rails
It used to work perfectly some time ago, so after some digging, I realised it might have something to do with my timezone.
In the headers of the Twitter response, one of them is:
date:
- Sun, 11 Apr 2010 16:53:34 GMT
Even though the time is actually 17:53:34 BST
I'm assuming the request is signed using BST time, and so it fails.
Anyone had this problem / found a fix for it?
The OAuth timestamp used in the signature is in the epoch time format.
You might want to inspect the Authorization request header, check for the oauth_timestamp and check what you are sending with this helpful online tool.
The difference between your epoch time and Twitter's (which you get in the response, as you wrote) should be in the +- 300 second frame.
Hope that helps!
Well, if the time is 17:53:34 BST, then it really is 16:53:34 GMT.
So, if the oauth library you're using can't cope with the server specifying the time in a different time-zone (are you certain that's what's causing the problem) then it could be a bug in the library.
(Not very helpful, I know - I don't use ruby and haven't done any oauth development myself.) Have you tried contacting the library developer(s)?